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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds context about the content (specific certification types) but does not add behavioral details like response format or pagination. This matches the 'bar is lower' scenario, but the extra info is content-focused rather than behavioral.

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, compact sentence that front-loads the subject and then lists the certificate categories with no filler. Every element adds value, and the structure is easy to scan.

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 parameterless, read-only getter with no output schema, the description covers the essential return content: the certification types and references. It does not specify exact output format, but that is secondary for a simple retrieval tool given the annotations and content enumeration.

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, so the description adds no parameter meaning—and none is needed. The baseline for 0 parameters is 4, and the description does not compete with schema (which is empty). It correctly provides no redundant parameter info.

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 names the resource (FEODE certifications) and enumerates specific types (BV + CCS classification, API licenses, ISO standards, awards), making the tool's purpose unambiguous. It clearly distinguishes from sibling tools, which focus on company profile, drill pipe specs, machining services, etc.

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 implicitly signals when to use this tool: whenever certification details for FEODE are needed. No sibling tool covers certifications, so no exclusions are necessary. The absence of explicit 'when not to use' is acceptable given the uniqueness of the resource.

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