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

No annotations are provided, so the description carries the full burden. It only poses a question and does not disclose return type, side effects, or any behavioral nuances. For a likely boolean query, the description gives no indication of output format or performance characteristics.

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 a single sentence with no waste, but it is under-specified. While concise, it lacks essential details about the tool's behavior, making it borderline between efficient and vague. It does not earn a higher score because it sacrifices necessary context for brevity.

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?

With one parameter, no annotations, and no output schema, the description should provide more context about the regulatory context, what 'Art. 31' refers to, and what a positive or negative result means. The current description is a fragment that leaves too many details for the agent to infer, making it incomplete for reliable use.

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 schema has one string parameter 'provider' with 0% description coverage. The tool description simply repeats the word 'provider' without specifying format, expected values, or meaning. This does not compensate for the lack of schema documentation, leaving parameter usage ambiguous.

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 function: determining whether a provider is a Critical Third-Party Provider under Art. 31. The resource and specific regulatory context are identifiable, and it is distinct from sibling tools like concentration_risk or health_check, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus sibling tools like concentration_risk or obligation_map. No context, prerequisites, or exclusions are provided. The user must infer from the name and description, which is insufficient for clear tool selection.

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