pennylane_get_agl_export

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the conditional-return behavior ("si prêt"), which usefully implies the export may not be ready yet, but it omits anything about auth, rate limits, or how long generation takes.

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 short sentences with zero padding; the core action is front-loaded and the conditional return detail follows immediately. Every sentence earns its place.

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 an output schema present and annotations covering the safety profile, the description is nearly complete for a simple single-parameter read. The only minor gap is the absence of any explicit routing against sibling get/create export tools.

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?

There is a single parameter with 100% schema description coverage ("Identifiant de l'export AGL"), so the schema fully documents it. The description adds no further meaning about the id's format or origin, making the baseline 3 appropriate.

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 states a specific verb ("Récupère le détail") and resource ("export Grand Livre Analytique"), which is clearly distinguishable from the sibling pennylane_create_agl_export by the retrieval framing. It does not, however, explicitly name any alternative tool for contrast.

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?

Usage is only implied: the note that it "Retourne le statut et l'URL de téléchargement si prêt" hints at polling for an asynchronously generated export, but there is no explicit statement of when to call this versus create_agl_export or get_fec_export, and no prerequisites or exclusions.

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