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

The annotations already provide readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds useful context: 'Inputs are validated server-side' and 'audited deliverable'. However, phrases like 'Gapup agent-payable C-suite expertise (RISK)' are unclear, and no additional side effects or behavioral traits are disclosed. No contradiction with 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?

The description is short but wasteful: it repeats the tool name in the first phrase, includes a specific company reference case that is not essential, and contains opaque jargon ('Gapup agent-payable C-suite expertise'). The core function is not front-loaded, and every sentence does not earn 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?

Given the high complexity (6 parameters, nested objects, no output schema), the description is incomplete. It does not explain what the structured deliverable contains, how outputs are formatted, or how the async/polling pattern works. The 'Reference case' is presented without instructions on how to adapt it, leaving the agent with insufficient information for correct invocation.

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 only 17% (only 'async' has a description). The description says 'send the documented case fields' but never explains what those fields are or their semantics. It adds no value beyond the schema and does not compensate for the low coverage, especially for the nested company, dataInputs, materiality, and targetFrameworks objects.

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 opens with 'Pilote de reporting durabilité', which is essentially the tool name, and then says 'Returns a structured, audited deliverable' without a specific action verb like 'generate' or 'analyse'. It does not clearly distinguish itself from the sibling 'sustainability_report' tool, and the 'Reference case' mention adds marketing context rather than functional clarity.

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?

No guidance is provided on when to use this pilot versus the full 'sustainability_report' or other ESG/sustainability tools. The reference case hints at CSRD wave 2 but never states conditions, alternatives, or exclusions, leaving the agent to guess.

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