betfair_navigation

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

No annotations are provided, so the description must carry the full burden. It discloses the return structure (nodes with properties) but lacks details on authentication, rate limits, destructive behavior, idempotency, or any side effects. Under-specified for a tool with no 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 short and includes a return type and an example. It is front-loaded with the core function. However, it could be more concise by removing the example line if not critical, but overall it avoids unnecessary 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?

Given the high number of parameters (9) and no output schema, the description is incomplete. It does not cover parameter semantics, output specifics beyond a snippet, or usage context. The example is vague and does not compensate for missing details.

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 does not explain any of the 9 parameters (e.g., nodeIds, alt, locale, maxResults, attachments). The agent has no guidance on parameter meaning or usage beyond the schema itself.

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 traverses a navigation graph (sport → group → event → market) and explicitly guides to feed market ids into betfair_market_prices. The verb 'traverse' and resource 'navigation graph' are specific and distinct from siblings.

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?

The description hints at usage by mentioning feeding market ids into a sibling tool, but does not provide explicit when-to-use, when-not-to-use, or alternatives among the many betfair siblings. The guidance is implied but minimal.

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