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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety profile is covered structurally. The description adds genuinely non-derivable behavioral context: no control token is required for this call, and the returned snippet is meant to be installed on the target site as proof of control. It stops short of describing rate limits or the exact snippet format.

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 with no filler; the core action is front-loaded and the auth exemption and intended use each add distinct information. Every sentence earns its place.

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 read-only one-parameter tool with annotations covering safety and no output schema, the description covers action, auth exemption, and purpose adequately. The only gap is the unspecified return shape/pagination, which is minor here.

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 0% for the single 'id' parameter, so the description must carry the load. "For any submission" does implicitly identify the id as a submission identifier, which partially compensates, and the schema supplies the UUID format and pattern. But it never names the parameter or confirms whether the id is a submission, project, or badge id.

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?

States a specific verb and resource: retrieve the public badge snippet for a submission. It is distinguishable from siblings like purchase_badge_waiver and verify_submission, but it never explicitly contrasts itself with them, so it stays at a clear-but-undifferentiated 4.

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?

"For any submission" plus "Installing it on the submitted website proves control" implies when this tool is useful (proving site ownership/control), which is real contextual guidance. However, it never states when not to use it or points to an alternative such as verify_submission, so usage remains implied rather than explicit.

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