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

Discloses paid usage with detailed payment flow, US coverage, and output format. No annotations provided, so description carries full burden; it lacks idempotency or caching info but covers key behavioral traits.

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?

Single paragraph that starts with core purpose, then details, then usage. Some redundancy (e.g., US coverage mentioned twice), but overall well-structured and 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?

Given 10 parameters and no output schema, description explains output format (0-100 score with breakdown) and payment flow for first call. Sufficient for correct invocation.

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?

Adds meaning beyond schema by explaining how parameters (precipitation, soil, etc.) combine into a risk score and the role of activity profiles. Schema already describes each parameter, but description provides context.

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?

Clearly states the tool computes an outdoor delay/disruption risk score, listing data sources and use cases. Differentiates from sibling 'get_delay_risk_demo' via paid status and full US coverage.

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 states purpose-built for scheduling decisions, US coverage only, and activity profile selection. Does not mention when to avoid or compare with siblings like 'get_forecast', but context is clear.

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