Prochain match d'équipe

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

The description warns that the tool returns strictly the next single match (caps lock emphasis) and must not be used for plural requests. It adds context beyond the annotations (readOnlyHint, etc.) by specifying the singular behavior and the prerequisite of resolving team numbers.

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 moderately long but well-structured with a clear purpose, warnings (using emojis and bold), and recommendations. It is front-loaded and every sentence adds value, though it could be slightly more concise.

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 tool's complexity (5 parameters, output schema exists), the description covers key aspects: core functionality, usage boundaries, and prerequisite steps. It does not detail error handling or edge cases, but overall completeness is high.

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 baseline is 3. The description adds value by explaining how parameters like 'categorie' and 'numero_equipe' identify the team, and recommends using ffbb_resolve_team for imprecise input. The 'force_refresh' parameter is also contextualized.

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 it returns the next match for a specific team ('Prochain match à jouer pour une équipe précise'). It distinguishes from sibling tools like ffbb_club for plural queries and ffbb_last_result, making the purpose unambiguous.

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 explicitly tells when to use (singular next match) and when not to (plural queries like 'matchs restants', 'calendrier'), directing to ffbb_club(action='calendrier') instead. It also recommends using ffbb_resolve_team for imprecise categories.

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