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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the scope (per vendor plus national block) and optional filter, but does not disclose return format, pagination, or any other behavioral traits. With annotations covering safety, a 3 is appropriate.

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?

One sentence with no waste. It front-loads the core purpose and includes the optional filter. Every word earns 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?

For a simple read-only status tool with one optional parameter and no output schema, the description is nearly complete. It could mention what the returned status values look like or how the vendor filter behaves, but the annotations and schema cover the essential safety and parameter semantics.

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 100%, so the single optional 'vendor' parameter is already documented in the schema. The description adds the context that the filter is optional and that it filters by vendor, but does not add meaning beyond the schema's 'Optional vendor id or name'.

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 ('status per vendor') and resource ('French e-invoicing (PA) status'), and mentions the national einvoicing_france block. It is clear about what the tool returns, though it does not explicitly distinguish it from siblings like vendor_facts or list_vendors.

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 implies usage for checking French e-invoicing status per vendor, and the optional vendor filter suggests a use case. However, it does not explicitly state when to use this tool versus alternatives like vendor_facts or support_deadlines, nor does it provide exclusions.

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