invalidate_pipeline_probe_cache

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

With no annotations, the description carries the burden. It usefully discloses that the operation performs no provider I/O and targets cached zero-payload probes. However, it does not say whether the invalidation is destructive to existing cached results, idempotent, or what happens afterward.

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?

One sentence with no filler. Every phrase ('cached', 'zero-payload', 'without provider I/O') contributes meaning, and the core action is front-loaded.

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?

The tool is simple and has an output schema, but the description omits the semantics of its only parameter and provides no scenario guidance. An agent cannot reliably determine how to populate or omit `provider`.

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?

Schema coverage is 0%, and the description never mentions the only parameter, `provider`, even though it is optional with a default empty string. The description adds no meaning about what values are valid, what the default behavior is, or how provider scopes the invalidation.

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?

Uses a specific verb ('Invalidate') and object ('cached zero-payload pipeline probes') and adds a distinguishing constraint ('without provider I/O'). It is unambiguous and does not merely restate the tool name.

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?

The description implies a context (cache invalidation that avoids provider I/O) but never states when to use this tool, when not to, or which sibling tool might be an alternative. There is no actionable routing guidance.

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