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

Annotations only give the generic mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds materially more — guest tier at 30 req/min, IP-based rate limit of 3/hour, key shown only once and must be stored, and that the guest tier changes once claimed by email or wallet. It also discloses how to authenticate downstream (api_key param vs. Authorization: Bearer header). This is exactly the context annotations cannot carry.

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?

Six short sentences, front-loaded with the outcome and benefit, then constraints, then credential handling, then endpoint availability. Every sentence carries operational information an agent would otherwise get wrong; nothing is redundant padding.

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 zero-parameter credential-issuing tool with no output schema, the description supplies everything an agent needs: what comes back (a key, shown once), what to do with it, its limits, and on which MCP endpoints the call succeeds. No obvious gap remains.

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?

Zero parameters, so per the rubric the baseline is 4. The description usefully confirms no signup input is needed ('no form, no email') and explains that the returned credential goes into an api_key parameter on other tools, though it adds no additional per-parameter detail beyond that.

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?

Opens with a specific verb and resource: 'Instant signup: returns an API key immediately', plus the scope ('no form, no email'). The final two sentences add endpoint-level scoping ('Available on the full MCP server /api/mcp. Not available on the read-only discover MCP /api/mcp/discover'), which lets an agent distinguish this from every sibling without opening a schema.

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?

Clearly implies when to call it — when you need an API key to pass to 'later buying tools' — and explicitly states where it is and is not available, which is a real exclusion. It stops short of naming specific sibling tools or saying when a non-guest/claimed-key path should be preferred, so not a 5.

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