check_trip_disruptions

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

Annotations already declare readOnlyHint=true (safe read), idempotentHint=true (same result), destructiveHint=false. Description adds important behavioral context: results may be incomplete/delayed/incorrect, informational only, and not emergency services. This exceeds minimal annotation value.

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?

The description is front-loaded with purpose and usage, then adds limitations. It is relatively long but each sentence adds value (use cases, limitations, payment detail). Minor redundancy (e.g., 'Informational only' appears twice in spirit) but overall well-structured.

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 no output schema, the description does not explain return values or structure. It covers usage, limitations, and purpose well but lacks output format details. For a tool with 8 parameters and no required fields, more guidance on what the agent receives would improve completeness.

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% with descriptions for all 8 parameters. The description provides overall context for the parameters (destination, origin, lat, lon, etc.) but does not add specific meaning beyond what the schema already explains. 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 checks for travel disruptions using a paid service, with specific verb 'Check' and resource 'travel disruptions' (result of x402 Travel Pulse). It distinguishes itself from sibling planning tools like plan_day_trip or find_transit_options by focusing on disruption awareness.

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: before departure or during a trip, with recurring updates on demand. Lists use cases (weather alerts, natural events, water/flood context) and exclusions (not emergency services, not substitute for official instructions). Provides clear alternative contexts.

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