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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context — a quota of 10 checks per hour — which an agent must know to avoid failing calls. It stops short of saying what happens when the quota is exhausted or what the check returns.

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?

Two short sentences, action stated first, rate limit immediately after. No filler or redundancy.

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 one-parameter trigger tool with no output schema, the description covers the action and the operational constraint (rate limit). It leaves open what the verification result contains and what an agent should expect at the quota boundary, which is a minor but real 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?

With a single parameter and 100% schema description coverage, the schema fully documents project_id including its pattern. The description adds no extra meaning about the parameter, so the baseline 3 applies.

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 — it checks the client's site for the badge — which is distinguishable from the sibling get_badge (which presumably reads badge state/embed info) because 'Checks ... now' implies triggering a live verification. It never names that sibling or explicitly contrasts the two, so the differentiation is inferable rather than stated.

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?

'now' hints that this forces an immediate, on-demand check rather than reading cached status, which is useful implied usage. However, there is no explicit guidance on when to call this versus get_badge, nor on preconditions beyond the rate limit.

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