List HoodGrow prepaid credit bundles

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

Annotations already declare read-only, open-world, idempotent, and non-destructive. The description adds behavioral context beyond annotations by explaining the credit spending mechanism (paid once via x402, then cheap wallet signatures) and reinforces the no-credentials requirement, matching the openWorldHint.

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 two sentences, front-loaded with the resource name and output structure. The second sentence adds valuable context about credit mechanics without waste, earning every word's place.

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?

Despite lacking an output schema, the description embeds the return format inline, making the tool fully self-contained. With annotations covering safety and zero parameters, there are no significant gaps in what an agent needs to know.

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 tool has zero parameters, so schema coverage is trivially 100%. The description doesn't need to explain params; it correctly omits any, and the baseline for no parameters is 4.

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 returns the 'Current prepaid credit bundle catalog' with an explicit data shape. It distinguishes itself from siblings by referencing buy_credits and the credit usage model, making it unambiguous that this is a read-only listing tool.

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: it's free, requires no credentials, and points to HOODGROW_USE_CREDITS for credit usage. While it implies this is the catalog to list before purchasing via buy_credits, it doesn't explicitly state when not to use it or name an alternative for listing.

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