apitennis_h2h

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

The description adds valuable context beyond annotations: the return shape, a warning that the shape is unverified and approximate, a note that `result` is an object unlike other methods, and authentication requirements via API_TENNIS_KEY. This helps set expectations and avoids surprises when inspecting the live payload.

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 multi-line but well-organized: purpose, return shape, caveat, example, and auth. Each section adds information, though the 'Also answers this' line adds some noise and could be removed. It is appropriately front-loaded with the main purpose.

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?

The description covers the return shape, provides an example, states authentication requirements, and includes an honest caveat about unverified shape. Missing details like error behavior or exact structure of 'recent form' are placeholders, but for a read-only H2H tool this is fairly complete, especially given the example and annotations.

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 coverage is 100%, so parameter meaning is already clear from the input schema. The description adds an example with concrete keys (1905, 1903) and a note about the `method` parameter's capitalization, but it does not substantially extend the schema's descriptions or explain the semantics of player keys beyond 'First player key.'

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 opens with 'Head-to-head history between two players, plus each one's recent form,' clearly stating the resource and the action. It distinguishes this tool from other tennis tools by focusing on H2H, and the 'Also answers this' line, while ambiguous, points to related 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?

The description implies usage for head-to-head queries but does not explicitly state when to use this tool over alternatives or when not to. The 'Also answers this' line hints at overlap with other tools but lacks clear selection guidance, such as 'Use apisports_football_h2h for football matches.'

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