ride_profile

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

No annotations and no disclosure of behavior. Whether the tool reads, mutates, or requires authentication is entirely unspecified. With zero annotation coverage, the description carries the full burden and fails completely.

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 two-word fragment is concise but entirely uninformative. Brevity here reflects under-specification rather than efficient communication.

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?

Completely inadequate. No output schema, no annotations, no parameter documentation, and a description that only echoes the tool name. An agent cannot determine what this tool does or how to call it.

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 'token' parameter has 0% schema description coverage. The description does not mention what the token is, whether it is required (it is not marked required), or how it relates to the profile retrieval.

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 'Passenger profile' is a noun fragment with no verb and no clear purpose. It is ambiguous whether the tool reads or writes a profile. Siblings ride_profile_show and ride_profile_set clearly delineate read/write, but this tool gives no such signal.

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 guidance on when to use this tool versus ride_profile_show, ride_profile_set, or food_profile. The agent has no basis for selecting this tool over its numerous siblings.

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