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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals key traits: the cost ($0.10 USDC), what the user gets (credits, priority access), limits (500 passes, max 5 per wallet), and the return value (payment instructions). It also outlines the subsequent action (send USDC, then confirm). This goes beyond the minimum by explaining the full process, though it does not detail the exact structure of the payment instructions.

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 well-structured with an introductory sentence, bullet points for benefits, and a closing note on next steps. It is slightly longer than strictly necessary but every sentence contributes value, and the bullet list improves scannability. It is not as tight as the two-sentence TDQS example, but it remains efficient.

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 tool with one parameter and no output schema, the description is thorough. It explains the membership costs, benefits, limitations, and the complete purchase flow (get instructions, send USDC, confirm). This is sufficient for an agent to understand how to call the tool and what to expect. It does not cover edge cases like refunds or failure modes, but those are not essential given the simple nature of the tool.

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?

The input schema has 100% coverage for the single parameter buyerWallet, so the schema already documents its format and purpose. The description adds a limit (max 5 per wallet) but that is a business constraint, not a parameter semantic detail. Therefore, the description adds little beyond the schema, warranting the baseline score of 3.

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 clearly states the tool's purpose: obtaining the RRG Agent Pass Phase 1 founding membership. It specifies the action ('Get your RRG Agent Pass') and distinguishes itself from sibling tools by detailing the exact next step ('call confirm_agent_purchase with your txHash'). This is a specific verb+resource with differentiation from related tools.

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 description provides clear context on when to use the tool (to start the membership purchase flow) and explicitly names the follow-up tool (confirm_agent_purchase). It also includes conditions like 'Max 5 per wallet' and 'Limited to 500 passes', which help the agent understand eligibility. However, it does not explicitly state when not to use it or mention alternative tools like initiate_agent_purchase, so it stops short of a 5.

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