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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true, and readOnlyHint=false. The description restates idempotency and scopes the operation to one site, but it does not disclose permissions, side effects such as notifications, error behavior, or response details. With annotations covering the safety profile, this is adequate but thin.

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, but the wording is awkward ('Once a badge a member', 'reads under an address') and the action is not front-loaded. It is concise yet clarity and structure suffer.

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 three-parameter mutation tool, the description covers target site, badge, member email, and idempotency, while annotations cover safety hints. It omits error behavior, return values, permissions, and prerequisites, which matters because no output schema exists.

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%; the schema documents site as named by list_sites, badge as id or name, and email as the member's address. The description clarifies site scope and that email identifies the member, but adds little beyond the schema. Baseline 3 is appropriate.

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 action: gives a badge to the member on the site named in site. It implicitly distinguishes awarding from create_badge, update_badge, and take_back_badge by focusing on assignment to a member, though it does not name those siblings. The phrase 'member who reads under an address' is awkward but still points to email.

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?

Implies use when assigning an existing badge to a member on a site and notes idempotency with 'giving it again changes nothing.' It does not explicitly say when to use create_badge, update_badge, or take_back_badge instead, nor does it mention prerequisites such as badge or member existence.

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