tab_tournament

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

No annotations provided. Description mentions return shape but does not disclose behavioral traits like rate limits, authentication needs, side effects, or what 'top markets' entails. Minimal behavioral context beyond output structure.

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?

Three sentences, front-loaded with purpose and example. Compact and readable, but could be more structured by separating return type and parameter hints.

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?

No output schema; description gives return structure but lacks details on parameter defaults (e.g., jurisdiction, numTopMarkets), error handling, or pagination. With 5 params and complex nested return, more completeness is needed.

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 has 5 parameters with 0% description coverage. Description only hints at numTopMarkets via 'top markets' but does not explain any parameter meaning or format. Fails to compensate for lack of schema descriptions.

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 returns tournament matches with top markets for tournament-structured sports (tennis, golf). Provides example Wimbledon Mens Singles. However, does not explicitly distinguish from siblings like tab_match or tab_competition.

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?

Implied usage: when you need tournament matches and top markets. No explicit when-not or alternatives. Sibling tools exist (tab_match, tab_match_markets), but no guidance on choosing between them.

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