set_destination

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, prerequisites, or authorization requirements. For example, it does not clarify whether setting the destination can be done before a ride is active or if it overrides a previous destination.

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 concise and free of unnecessary words, which is appropriate for a simple setter. However, it is so terse that it sacrifices valuable contextual information that could have been included without harming conciseness.

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 the ride-hailing workflow and sibling tools (e.g., login, request_ride, set_pickup), the description is incomplete. It does not mention whether the user must be authenticated or currently have an active ride, nor does it explain the impact of setting a destination (e.g., whether it triggers fare estimation). With no output schema, the agent also has no idea what the return value represents.

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 input schema has 100% description coverage for the single parameter, 'location', which is already well-explained as a destination address or place name. The description adds no additional semantic meaning, so the baseline score of 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's purpose: setting the destination for a ride. It uses a specific verb ('set') and resource ('destination'), and is easily distinguished from the sibling tool 'set_pickup' which handles pickup location.

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 usage guidance is provided. The description does not indicate when this tool should be used (e.g., after requesting a ride) or when it should be avoided, nor does it reference any alternative tools. This leaves the agent to infer the appropriate context.

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