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

No annotations are provided, so the description must fully disclose behavior. It mentions the report is generated (HTML/PDF) but does not clarify if this tool modifies data, requires authentication, or is read-only. The description also references data provided by the agent but does not explain side effects.

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 a single paragraph but front-loaded with the key usage condition. It is concise, covering purpose, output format, recipient, and data source without unnecessary words. However, it could be more structured with bullet points for clarity.

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 has 15 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return value, how to trigger PDF generation, or the meaning of many optional parameters. The directive to direct clients to /api-ia adds confusion.

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 description coverage is 0%, so the description must compensate. It mentions 'recettes/dépenses/honoraires/solde' which map to four parameters, but most of the 15 parameters (e.g., lieu, agence_nom, date_emission) are not explained. The required parameters proprietaire_nom and periode are implied but not elaborated.

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 the tool is for generating a simplified management report for the owner, with specific triggers: end of quarter, fiscal year, or upon request. This distinguishes it from sibling tools like quittance_loyer or regularisation_charges.

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 starts with 'QUAND il faut rendre compte au propriétaire' providing explicit usage context. It mentions the report is HTML with optional PDF via another endpoint. However, it does not explicitly state when not to use or list alternatives, and the final sentence about directing the client to /api-ia is somewhat ambiguous.

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