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

With no annotations provided, the description carries the full burden. It discloses the cost, benefits, limits (500 passes, max 5 per wallet), and that the tool returns payment instructions rather than executing the purchase. This is transparent about the tool's role and the process, though it doesn't detail what the payment instructions look like or any potential side effects.

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 moderately long but well-structured with a clear intro, bullet points for benefits, and a final instruction. Every sentence adds value—detailing cost, benefits, limits, and next steps. It is front-loaded with the main purpose and avoids fluff, though it could be slightly more compact without losing clarity.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description provides sufficient context: what the pass is, its value, limitations, and the follow-up required. It covers the user's journey well, though it doesn't describe the exact format of the payment instructions, which would be helpful but not critical.

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 schema already fully describes the single parameter buyerWallet with its pattern and description. The description adds no new parameter semantics but provides context (max 5 per wallet) that relates to the parameter's usage. Since schema coverage is 100%, the description's lack of parameter-specific detail is acceptable, earning the baseline score.

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: to get the RRG Agent Pass Phase 1 founding membership. It specifies the action (get), the resource (Agent Pass), and the context (membership). It also distinguishes from siblings by noting it returns payment instructions and directs the next step to confirm_agent_purchase, differentiating it from initiate/confirm purchase 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 a clear usage flow: call this to receive payment instructions, send USDC, then call confirm_agent_purchase with the txHash. It implies when to use this tool (to start the pass purchase) and names the follow-up tool, but does not explicitly state alternatives or when not to use it. Still, the guidance is strong and context-rich.

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