get_badge

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

With no annotations, the description carries the burden of disclosing behavior. It implies a read-only operation returning a URL, but does not mention side effects, permissions, error handling, or what happens if the slug is invalid or the service is not verified. Gives a basic idea but lacks explicit behavioral details.

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 two concise sentences, front-loaded with the primary action and followed by a practical use case. No unnecessary words or repetition, achieving high efficiency.

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 tool with one parameter and no output schema, the description covers the main purpose and a common use case. It does not elaborate on authentication, URL format, or conditions for verification, but these are not critical for basic usage. Overall, sufficiently complete given the simplicity.

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 fully covers the slug parameter (100% coverage), so baseline is 3. The tool description adds no additional detail about the parameter itself, though 'for a verified service' hints at a constraint. No significant enrichment beyond the schema.

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 purpose: obtaining the ClearedIndex trust badge URL for a verified service. It uses a specific verb ('Get') and resource (trust badge URL), and mentions a use case (embedding verification status), making it distinct from sibling tools like get_trust_score or get_cleared_status.

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 provides a use case ('useful for embedding verification status') but does not explicitly contrast it with sibling tools or specify when not to use it. Lacks explicit when/when-not guidance, but the purpose is clear enough to guide selection.

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