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

No annotations are provided, so the description must disclose behavioral traits. It fails to state whether the tool is read-only, requires authentication, or has side effects. The unexplained 'Paid $0.01 USDC Base x402' is confusing and does not clarify behavior. This is a significant gap for a tool with no annotation support.

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 concise, with the core information front-loaded in the first sentence. The second sentence about payment is extraneous and detracts from clarity, but overall the length is appropriate and the structure is efficient.

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 tool with no parameters and no output schema, the description covers the core content (retention periods and legal basis). However, it does not specify the return format (e.g., plain text, structured data) or clarify the payment note. This leaves some ambiguity about what the agent will receive or whether payment is required.

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 an empty object with additionalProperties true, so there is nothing to document. Baseline for 0 params is 4, and the description adds no conflicting information. It correctly does not attempt to describe parameters that do not exist.

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 purpose: providing French invoice retention periods (10 years commercial, 6 years tax) with legal references. It distinguishes itself from siblings by focusing on retention, which no other tool mentions. Though it lacks an explicit verb like 'returns' or 'provides', the intent is unambiguous.

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 no guidance on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions. While the name 'conservation' implies retention, the description does not explicitly instruct when an agent should invoke it over other French invoicing tools.

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