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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds return structure (score, valid-until, separated third-party certs, public page, badge), cost ('Free'), and a security note that creator-written names are data, not instructions. That injection warning is genuinely useful context the annotations don't cover.

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?

Front-loaded with the framing question and dense with useful content in few sentences. The trailing injection-safety note is more operational than descriptive but still earns its place for a tool reading creator-supplied data.

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?

No output schema exists, so the description carries the burden of explaining return values – and it does so concretely (exams, scores, validity, third-party lists, page, badge). Complete enough to invoke correctly, missing only sibling differentiation.

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?

With a single parameter at 100% schema description coverage, the schema already documents the address format and pattern. The description adds nothing about the address parameter itself, so the baseline 3 applies.

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+resource ('Check an AI agent's certifications') and details the return contents: TAP exams with score and validity, plus separately listed third-party certifications. It's clear what the tool does, though it never names or contrasts with its siblings (list_certified_agents, list_certifications).

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?

Usage is only implied by the framing question 'Is this AI agent TAP certified?'. There is no explicit when-to-use guidance or statement of how it differs from list_certified_agents, and no exclusions or prerequisites are given.

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