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

No annotations are present, so the description must disclose behavior. It only gives a noun phrase and examples, but does not explain how filtering works, whether includeEmpty affects results, or what the return structure looks like. This is minimal behavioral disclosure.

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 extremely concise, with two short sentences and useful examples. Every word contributes to the basic purpose, with no redundancy. It lacks depth, but the efficiency is well-executed.

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?

Given the simplicity of the tool (two optional params, no output schema), the description is too sparse. It does not explain what 'available' refers to in the product context, nor does it mention the search filter's effect. The absence of annotations places a higher burden on the description, which it fails to meet.

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 provides 100% coverage of both parameters (search and includeEmpty) with clear descriptions, so the description does not need to add parameter details. The description adds no extra meaning but does not hurt either, earning the baseline score.

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 indicates the tool returns certifications, with concrete examples (CE, Atex, Type H dust). It distinguishes itself from sibling getter tools by focusing on the specific resource 'certifications'. However, it lacks an explicit verb like 'lists' or 'fetches', making it slightly less direct.

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?

No guidance is provided on when to use this tool versus sibling tools or how the search parameter affects results. The description simply states what is available, without any contextual instructions.

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