pipeline_monitor_data

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description says the tool 'refreshes data', which connotes a state-changing operation (reloading/regenerating data), while the annotations declare readOnlyHint=true. That is a direct conflict about whether the tool mutates anything. The description also adds no other behavioral context (auth needs, cost, side effects), so it fails the one job it had here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is structurally clean. However, the brevity is under-specification rather than economy: the one sentence conveys almost no actionable information, so it does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an undocumented parameter, no output schema, and only a single readOnlyHint annotation, the description is far too thin. It leaves the agent unable to resolve the read/write ambiguity, the meaning of the 'database' argument, or when this is preferable to pipeline_monitor or pipeline_status.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional 'database' parameter has no schema description (0% coverage), and the description never mentions it at all. The agent cannot tell whether 'database' scopes which database's pipeline data is refreshed, whether omitting it means all databases, or what values are valid. The description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb (refresh) and an object (data for the Pipeline Monitor app), so the general intent is graspable. But it never says what 'refresh' concretely does or what data is involved, and it does nothing to distinguish itself from siblings like pipeline_monitor, pipeline_status, or pipeline_errors. Purpose is vague rather than tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus pipeline_monitor, pipeline_status, or any other sibling. No preconditions, no exclusions, no alternatives are named. The agent is left to infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.