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

With no annotations, the description carries full burden. It frames the tool as a read operation ('Returns') and discloses what is included, which gives a clear behavioral picture for a simple no-parameter getter. It stops short of detailing error conditions, auth needs, or response format, but for this simple tool the disclosure is solid.

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?

Two sentences, front-loaded with the core purpose, and each clause adds information (requirements, included contents). No wasted words or redundancy.

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 simple 0-parameter tool with no output schema, the description covers the essential return content (x402 payment, burn requirements, instructions, addresses, amounts). It is sufficient for an agent to know what to expect and when this tool is relevant, though a bit more detail on the response structure could push it to 5.

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 the description cannot add parameter meaning; the baseline of 4 applies. Schema coverage is trivially 100% with no properties, so no parameter documentation gap exists.

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 it 'Returns the x402 payment requirements and $MEGACHAD burn requirements for looksmaxxing', using a specific verb and resource. It also enumerates included elements (step-by-step instructions, contract addresses, amounts), distinguishing it from siblings like get_looksmaxx_plan.

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 implies usage when you need payment/burn requirements for looksmaxxing, but provides no explicit when-to-use guidance or mention of alternatives. Given sibling tools like get_looksmaxx_plan exist, the overlap is not addressed, leaving usage context entirely implicit.

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