Get Matches

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

Annotations already provide readOnlyHint=true, so the description correctly adds behavioral context like 'returns enriched match data' and timezone conversion, without contradiction. It does not detail other aspects (rate limits, auth) but that is acceptable given readOnlyHint.

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-load the purpose, then list filters and return details. No redundancy or fluff; every sentence adds value. Efficient and clear.

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?

Covers main filtering, return content, and timezone option. However, it omits default behavior (all matches? limited?), output structure, and pagination. Mostly complete for typical use, but lacks a few 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 coverage is 100%, so each parameter has a description. The tool description summarizes filters and mentions timezone conversion, but adds minimal new meaning beyond the schema. Baseline of 3 is appropriate.

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 explicitly states 'Query FIFA World Cup 2026 matches' with specific filters (date, team, group, etc.) and return content (enriched match data, venue details, timezone conversion). It clearly distinguishes from siblings like get_schedule or get_teams by specifying the resource and output detail.

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 lists available filters and output, but does not explicitly state when to use this tool versus alternatives (e.g., get_schedule for a simple list, get_standings for table). Lacks 'when to use' or 'when not to use' guidance, relying on implied context.

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