Raw Yango Tech Retail API call

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

While annotations already indicate destructive and non-read-only behavior, the description adds important context beyond them: it warns 'this tool can perform writes' and discloses that '5xx/network errors are never retried'. It also clarifies that every endpoint uses POST, which is a behavioral trait not covered by 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?

The description is front-loaded with the purpose ('Escape hatch') and packs essential usage, examples, and cautions into three sentences. The list of endpoint patterns, though lengthy, earns its place by clarifying scope.

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?

For a raw API tool with no output schema, the description covers the when, how, and safety considerations comprehensively. It addresses method (POST), path format, body, retry behavior, and write risk, making it self-sufficient for agent selection and invocation.

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 100%, so baseline is 3. The description echoes the path example and body object but adds no new meaning beyond the schema's own descriptions, which already detail relative path usage and default JSON body.

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 identifies the tool as an 'escape hatch' for direct calls to any Yango Tech Retail B2B endpoint, with a specific verb ('call') and resource ('endpoint'). It lists example paths that lack dedicated tools, distinguishing it from sibling tools.

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?

Explicitly states when to use it: 'for paths without a dedicated tool', and provides concrete examples. It also instructs on usage ('pass a relative path like... and the body object') and cautions about non-retry behavior for 5xx/network errors.

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