Bilan détaillé de saison

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

Annotations already indicate readOnly, idempotent, non-destructive, and openWorld. Description adds output structure and cache control via force_refresh, but does not disclose additional behavioral traits beyond 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?

Description is concise and well-structured: purpose first, then output details. No redundant sentences. Could slightly shorten the listing of return fields, but overall efficient.

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 output schema exists, description adequately covers the main use case and return fields. Mentions aggregation and cache override. Missing info on data freshness limits or pagination, but not critical for this tool.

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%, and description reinforces the purpose of the three key parameters as a team identifier and force_refresh for cache. Adds some context but schema already handles parameter semantics well.

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?

Title and description clearly state the tool provides a detailed season report for a specific team. It distinguishes itself from generic 'bilan' by mentioning per-phase aggregation, but does not explicitly differentiate from siblings like ffbb_team_summary.

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?

Provides an example query ('Quel est le bilan de la saison des U11M1 ?') and implies use for team-specific season questions, but does not specify when not to use or contrast with alternatives such as ffbb_bilan or ffbb_team_summary.

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