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

Goes well beyond the annotations: requires the user to be logged into their Tchin account (prompted on first use), defaults to the last 30 days with a hard one-year cap, applies the same filters as account history, and returns a download URL valid 24 hours that only opens for the authenticated holder. These are real constraints an agent must know before calling.

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?

Information is front-loaded: audience and access condition first, then what is produced, period limits, and return value, ending with the usage trigger. Dense but each sentence carries distinct facts; the opening clause is slightly overloaded.

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?

With no output schema, the description supplies exactly what it must: the return value (a 24-hour download URL restricted to the logged-in holder) and the operational envelope (default and maximum period, filter parity with history). Nothing essential for a correct call is missing.

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 57% and the description supplies key semantics the schema lacks: the default period (30 days) and the one-year maximum for du/au, plus the fact that the other filters mirror account history. The enum parameters (mode, sens, statut, pays) are left to the schema, so it does not fully compensate for the gap.

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?

States a specific verb and resource: "Fait le relevé des transactions en PDF, au format officiel des documents Tchin", scoped to a period and filters. This is clearly distinguishable from siblings such as mes_transactions (raw history) or rapport_ventes (sales report).

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?

Explicit trigger given: "À utiliser dès que l'utilisateur demande un relevé, un PDF ou un document de ses transactions." It does not name an alternative (e.g. mes_transactions for a non-PDF listing), so no explicit exclusion, but the positive routing condition is unambiguous.

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