get_yango_delivery_link

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

Annotations indicate readOnlyHint=true and destructiveHint=false, and the description adds context that pricing and order placement happen on Yango's side, not through this server. This clarifies the non-destructive, link-generating nature. No contradiction with annotations.

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 sentences, front-loaded with the main purpose, and each sentence adds value. No wasted words.

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?

Output schema exists, so missing return value description is acceptable. However, the tool interacts with an external service (Yango), and the description lacks details on prerequisites (e.g., Yango app, region) or external dependencies.

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%, and the description only mentions 'between two points' without explaining the coordinate parameters (pickup_lat, etc.). It fails to add meaning beyond the schema 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?

Description clearly states it gets a Yango booking link for a delivery between two points, and distinguishes from sibling tools (e.g., airtime, data, food) by specifying the Yango-specific purpose. It uses a specific verb ('get') and resource ('Yango delivery link').

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?

Description explains when to use the tool: to get a link for a delivery. It implies it's not for direct API access by noting 'until direct API access is enabled'. No explicit alternatives or exclusions are given, but the context of siblings suggests it's unique.

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