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

The description adds meaningful behavior beyond the annotations: it requires Authorization Bearer JWT, refuses unearned badges with the earned list, and clarifies that the badge appears across public surfaces. It does not over-promise and aligns with the non-read-only, non-destructive hints.

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 compact and front-loaded with the core action, then adds the prerequisite and failure behavior in two efficient sentences. Every sentence earns its place with no filler.

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 setter with no output schema, the description covers the prerequisite, the validation rule, the auth requirement, and the effect of the action. An agent has everything it needs to call the tool correctly.

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 badge parameter is already described as 'one of your earned badges' with examples. The description reinforces this and adds the validation behavior, but does not substantially extend what the schema already communicates.

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 uses a specific verb ('Pick') and names the resource ('badge') plus the exact scope of the action — which badge fronts identity on public surfaces. It clearly distinguishes itself from related page_* tools by emphasizing 'YOUR earned badges' and the public-surface effect.

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 prerequisite: call page_me first to see earned badges via `badges`. It also explains the failure mode for unearned badges. It does not explicitly compare against alternative tools like page_cover_set, but the usage context is clear enough.

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