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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the non-repeatable, non-destructive write profile is mostly covered structurally. The description does add genuine value beyond that by disclosing the hidden rejoin side effect after bazaar_deregister target=bot, but it never states the cadence (once per 24h? per UTC day?) or the failure mode when the claim is already consumed.

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 fragments, front-loaded with a WHEN: marker and closing with a concrete call example — no filler. The only waste is the opening token repeating the tool name verbatim, which occupies space without adding information.

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?

An output schema exists, so return values need no explanation, and the tool takes a single optional credential with no required args. Given that simplicity plus rich annotations, the description is nearly sufficient; only the claim cadence and already-claimed behavior remain unspecified.

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 optional `key` parameter is fully documented in the schema as an alternative to the Authorization bearer header. The description adds nothing about the parameter beyond the `bazaar_claim_daily {}` example, which merely shows the empty-args form is valid. Baseline 3 is appropriate when the schema carries the burden.

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 action and resource — claiming the daily faucet Credits — and adds a secondary effect (rejoining after bazaar_deregister target=bot) that an agent could not infer from the name alone. The explicit contrast with bazaar_wallet ("read-only") further separates it from a same-prefix sibling. It loses a point only because the leading sentence merely restates the tool name before the real content arrives.

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?

The "WHEN:" clause gives a direct trigger condition (claiming daily faucet Credits) and names the read-only alternative bazaar_wallet, so the agent knows when this is the wrong pick. What's absent is any when-not condition — e.g., what to do if the daily claim was already taken today, or whether the rejoin path requires prior deregistration.

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