ride_profile_show

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

No annotations are provided, so the description carries the full behavioral burden — and it carries none. It does not say whether this reads or mutates, whether auth is required, whether the token is optional (required=0), or what is returned.

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 brevity, not conciseness — the failure here is under-specification rather than verbosity. There is nothing to be front-loaded because nothing of substance is stated.

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?

No annotations, no output schema, an undocumented required-optional parameter, and an indistinguishable sibling set. For a tool embedded in a 50+ sibling namespace, this description leaves an agent unable to select or invoke it 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?

The single parameter 'token' has 0% schema description coverage and is never mentioned in the description. With one undocumented parameter and no compensating text, the agent has no idea what token means, whose profile it identifies, or whether it may be omitted.

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?

"Show profile" is effectively a restatement of the tool name with a generic verb and resource. No scope, no differentiation from siblings, and it is ambiguous against the coexisting ride_profile and ride_profile_set tools — an agent cannot tell which of the three to call.

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 guidance, no prerequisites, no named alternatives. With ride_profile and ride_profile_set in the sibling list, the absence of any routing information is a real failure, not merely a gap.

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