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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one behavioral trait (it deliberately does not return the full Pine code) but then lists return fields that an existing output schema already documents, so marginal added value is modest.

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 tightly packed sentences, with the core purpose front-loaded before the return-detail sentence. Efficient overall, though the enumeration of return fields is partly redundant with the output schema.

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?

For a single-parameter, read-only, idempotent tool with full annotation coverage and an output schema, the description supplies enough: what it inspects, that it withholds the Pine code, and what it returns. Only the linkage to the sibling export tool is left implicit.

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 ('Script ArenaScript (20 000 caractères max)'). The description does not add any syntax, format, or constraint detail beyond what the schema already states, so the baseline of 3 applies.

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 and resource (inspect whether an ArenaScript strategy can be faithfully exported to Pine v5) and signals a difference from a full export by noting it avoids returning the whole Pine code. It is clear on its own, but does not name the relevant sibling (export_to_tradingview), so the differentiation requires inference.

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 phrase 'sans renvoyer tout le code Pine' suggests this is a lightweight feasibility check to run instead of a full export, but no explicit when-to-use, prerequisites, or named alternative is given. The agent can infer the context but receives no direct routing guidance.

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