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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds that the returned design includes 'its settings' and gives the underlying REST endpoint, but discloses nothing about errors on unknown ids, permissions, or payload shape.

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?

Two short, front-loaded fragments with no filler; the resource is stated before the endpoint. Slightly telegraphic (no explicit verb phrase), which keeps it just under a 5.

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 single-parameter read tool with annotations and no output schema, the bare statement of what is returned is the minimum viable. Since there is no output schema, more detail on what a design object contains would have helped the agent decide whether this call is sufficient.

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 coverage is 100% for the single design_id parameter, so the schema already carries the semantics. The description adds no format, range, or sourcing detail beyond what the schema states.

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?

Names the resource ('One badge or certificate design') and implies retrieval via the endpoint 'GET /v1/designs/{design_id}'. It contrasts implicitly with the plural search sibling by saying 'One ... design', but never names accredible_search_designs explicitly.

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 when-to-use guidance: it does not say to call this when you already know the design_id versus using accredible_search_designs to find one. The only hint about where an id comes from lives in the schema's parameter text, not the description.

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