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

Annotations already mark the tool as read-only and non-destructive. The description adds useful boundary context, clarifying that the tool returns a scope statement about ScoreInnov.com rather than an audit or legal judgment. It does not describe the exact return shape, but for a static, no-input informational tool the transparency is adequate.

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?

A single dense sentence front-loads the core subject, enumerates specific examples in a compact parenthetical, and ends with a clear usage hook. No words are wasted and the structure is easy to scan.

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 zero-parameter, low-complexity informational tool, the description explains what it is, what it is not, and when to use it. It does not specify the output format, and no output schema exists, but the remaining ambiguity is low for invoking this tool correctly.

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 input schema has zero parameters and full coverage, so the baseline is 4. There are no parameter meanings to explain, and the description appropriately focuses on the tool's purpose rather than inputs.

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 clearly states the tool's subject: what ScoreInnov.com does ('test gratuit', 'scanner SIREN') and does not do ('pas un audit', 'pas de conseil juridique'). This is specific enough to distinguish it from the sibling data-analysis tools, though it lacks a direct imperative verb and relies on the name for context.

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?

The phrase 'a utiliser pour toute question de confiance' is an explicit usage trigger, and the exclusions 'pas un audit, pas de conseil juridique' indicate when this tool should not be relied upon. It does not name alternative sibling tools, but for a no-parameter informational tool this is a minor gap.

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