ride_headsup

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether this is a read or a write, not whether it requires auth (the token param implies it), and not what a "heads-up" does or triggers. For an unannotated tool this is a complete failure of behavioral disclosure.

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 words is not conciseness but under-specification; there is nothing to front-load because no substance was written. It fails to earn its place only by omission, not by verbosity.

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?

With zero annotation coverage, 0% schema description coverage, no output schema, and two undocumented parameters, the description does not provide anything close to what an agent needs to invoke this tool correctly.

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 0% for both parameters. The description says nothing about token (presumably an auth credential) or ride_id (presumably the ride in question), so it adds zero meaning beyond the bare property names.

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?

"Cancellation heads-up" gestures at ride cancellation notification but gives no verb or defined action — it restates the name (ride_headsup) rather than stating what the tool does. An agent cannot tell whether it sends, registers, or retrieves a cancellation notice, nor how it differs from sibling ride_cancel.

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?

No when-to-use, when-not-to-use, or alternative guidance is present. With siblings like ride_cancel and ride_status nearby, the description gives no condition that selects this tool over them.

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