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

Discloses polling behavior (wait ~40s, reuse the same jobId), link validity, and quota impact ('ne consomme aucun quota'). This adds meaningful behavioral detail beyond the 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?

Two dense sentences with the core purpose placed first and behavior details following. No filler or repeated schema information.

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 the essential operational details: source tool, threshold, wait time, retry semantics, output type, and quota impact. With an output schema present, nothing critical 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?

The schema already documents jobId, and the description reinforces its origin (from basile_export) and its reuse across polls. This goes beyond the bare schema definition.

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 action (follow/poll an export launched by basile_export) and a clear result (returns a direct download link). It also distinguishes its scope ('FICHIER' and 'au-delà de 500 lignes') from the general export flow.

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?

Explicitly ties usage to a prior basile_export call and defines the relevant condition (file exports over 500 rows). It lacks a formal 'when not to use' or alternative comparison, but the intended context is clear.

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