wait_for_cdn_freshness

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

With no annotations, the description fully discloses key behaviors: single-vantage probe (us-east-1), timeout returns isError=true, and suggests fallback. Does not cover rate limits or concurrency, but adequate for a polling tool.

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?

Two well-structured paragraphs with bold for key points. Every sentence adds value; no filler. Front-loaded with purpose and usage, then details.

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?

Covers purpose, usage, behavior (single vantage, timeout), error handling (isError=true), and fallback suggestion. No output schema, but return behavior is explained. Complete for a polling tool with moderate complexity.

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 100%; description adds modest context like 'from a preceding upload' for sha256 and default for timeout_ms, but does not significantly enhance the schema's clarity. Baseline 3 is appropriate.

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 clearly states the tool polls the CDN for a mutable blob URL to match expected SHA-256 or timeout. It distinguishes mutable from immutable URLs, making the purpose unambiguous and distinct from siblings.

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?

Explicitly says when to use (after re-upload to mutable key, when end-user-visible URL must reflect new content) and when not (immutable URLs need no waiting). Mentions fallback behavior on timeout, providing clear guidance.

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