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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description usefully adds the scope restriction and the downstream purpose of the return value (paste it back into the lab), but it never addresses idempotentHint=false — an agent cannot tell why repeating the call may produce a different result, or what happens with an expired or malformed learner code.

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 short sentences, front-loaded with scope and trigger before the return value; nothing is padding. There is mild redundancy between 'returns a receipt proving…' and 'Returns a receipt to paste back into the lab', which costs it the top score.

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?

With one required parameter, no output schema, and full annotation coverage, the description covers what matters: who it is for, when to call it, what goes in, and what comes back. The only missing piece is error/retry behavior for an invalid or already-used learner code.

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% and the single parameter carries its own description plus a UUID pattern, so the schema does the heavy lifting. The description only echoes that the code is 'shown in the lab', adding no new meaning about format, lifetime, or failure modes.

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 — it returns a receipt proving the learner connected an MCP client to this server — and scopes it to a named lab ('Tools, not vibes'). That is far more specific than any sibling (verify_badge, check_spec, validate_cartridge), so an agent can distinguish it without opening the schema.

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?

It gives an explicit trigger ('Use when a learner asks for their lab receipt and gives their learner code') plus a hard exclusion ('For the Slop Curriculum's “Tools, not vibes” lab only'). It does not name an alternative tool for adjacent receipt/badge needs, which keeps it just short of a 5.

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