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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering safety. The description adds that it returns public identity information and its fraud-check purpose. It doesn't describe any edge cases or behavior beyond that, but that's minor given the simple nature of the tool. No contradiction.

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, well-structured sentence that front-loads the main purpose and includes a parenthetical with concrete examples and the use case. Zero wasted words.

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-param, read-only tool with no output schema, the description provides enough context: what it returns (identity details), examples of that data, and the practical use. It could mention the exact output format, but the examples and purpose suffice. Siblings are clearly unrelated.

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 tool has zero parameters, and the schema is empty with 100% coverage. Per the baseline for 0 params, a score of 4 is appropriate. The description doesn't need to add parameter info since there are none.

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 provides the public identity of the site editor, listing specific data points (TENDIL COURTAGE, SIREN, ORIAS, categories). This is a specific verb+resource, and the sibling tools (calculer_pfu, simuler_interets_composes, etc.) are all unrelated, so it's easy to distinguish.

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 description gives a clear use case: to verify the site isn't fraudulent. It doesn't explicitly say when not to use it or name alternatives, but given the distinct siblings and the stated purpose, the context is clear enough. Lacks explicit exclusions.

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