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

Annotations already establish the safe read-only, idempotent, closed-world profile, and the description goes well beyond them by disclosing exactly what is validated (RS256 signature against the published key, issuer fields, dates) and what the response contains (earner, timestamp, evidence, game-run verification). This is the kind of behavioral detail annotations cannot express.

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?

Three sentences, front-loaded with the core action and domain, then the accepted inputs, then scope. Dense but every clause carries information; the first sentence is long but not padded.

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 verification tool, the description covers what is checked, what is returned, and the scope limit, which is sufficient even without an output schema. It does not say what happens on a failed or unverifiable badge, which is the one remaining gap.

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 coverage is 100% and the parameter description already enumerates all three accepted forms (compact JWS, credential URL, verify link). The description restates the same three formats and adds only the minor hint that the JWS may come "from a baked badge," so it contributes little 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 names a specific verb and resource ("Check an Open Badge issued by learn.slopped.site") and narrows the domain to Slop Curriculum and Slopbox game badges (cart-*). It does not explicitly contrast with siblings like validate_cartridge or check_spec, but the domain scoping is specific enough that an agent can tell what this tool covers.

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?

"Use when someone shares a badge" gives a clear triggering condition, and "Only verifies learn.slopped.site badges" states an explicit exclusion. There is no mention of alternative tools for non-learn.slopped.site badges, so the routing is slightly incomplete.

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