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

With no annotations provided, the description carries the full behavioral-transparency burden. It discloses pricing, global coverage, and the deterministic/citation-locked nature of compensation letters, but omits authentication needs, rate limits, return format, and explicit read-only/mutation status—significant gaps for an API 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?

The description is front-loaded with the core purpose and then structured as a clear endpoint list. It is somewhat long and contains redundancy (repeated 'TransitPulse') and dense regulatory detail, but the length is largely justified by the 16-endpoint scope and the need to convey the compensation engine's legal basis.

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 description covers the overall domain and endpoint selection well, but with 37 parameters and no output schema, it does not explain which parameters are relevant for each endpoint (e.g., which compensation fields are required for 'check' or 'letter') or what the return payloads look like. The schema covers parameter meanings, so the description is minimally adequate but leaves substantial gaps.

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 description coverage is 100%, so the baseline is 3. The description adds notable value for the required 'action' parameter by mapping each enum value to an endpoint behavior and price, which the schema does not do. Other parameters are already fully described in the schema, so no further compensation is needed.

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's role as 'global public transit intelligence' and a 'compensation recovery engine', with a specific verb and domain. It lists 16 endpoint actions with one-line descriptions, making the tool's scope and purpose immediately identifiable and distinguished from sibling 'pulse' tools.

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 endpoint list provides clear context for choosing among actions (status, delays, trip, letter, etc.) with pricing and brief semantics. It lacks explicit exclusion guidance or named alternatives, so it does not quite reach a 5, but the usage context is strong.

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