Penny Press

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

No annotations are provided, so the description carries the full burden. 'Get' and the enumerated read-only fields imply a safe retrieval with no side effects, and it usefully discloses the return payload shape. However, it says nothing about authentication requirements, whether the price is cached or live, or any rate limits.

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?

A single front-loaded sentence that states the action, the resource, the returned fields, and the consumer's motivation with zero wasted words.

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 one-parameter, no-output-schema tool this is nearly complete: it substitutes for a missing output schema by naming the returned fields. It stops short of describing error behavior (e.g., unknown slug) or freshness of the payment data, which would round it out.

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?

Schema description coverage is 100% and the single 'slug' parameter is already documented with an example in the schema. The description adds no syntax, format, or validation detail beyond that, so the baseline 3 is appropriate.

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?

States a specific verb ('Get'), a specific resource ('x402 payment details for one essay'), and enumerates exactly what the payload contains (price, network, asset, recipient wallet). This is clearly distinct from the sibling list_essays, which is a bulk listing rather than a per-essay payment lookup.

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 trailing clause 'so a machine buyer knows how to pay' gives clear context for when the tool is needed (a buyer preparing a payment). It does not name an alternative or state when not to use it, but for a single-purpose lookup tool the usage context is unambiguous.

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

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

With no annotations, the description carries the full burden. It usefully discloses the payment model (x402, USDC on Base) and that full text is free to humans but paid for machine reads, which is meaningful behavioral context. It does not state whether the listing call itself is free, whether authentication is needed, or any rate limits.

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 tight sentences with zero waste: the first front-loads what is listed and returns, the second adds the access/pricing constraint. Every clause earns its 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?

For a no-argument list tool with no annotations and no output schema, the description compensates well by enumerating returned fields and explaining the human-vs-machine access model. It omits pagination/volume expectations and whether the listing itself requires payment or auth.

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 takes zero parameters, so the baseline is 4 under the rubric. The description goes slightly beyond that by embedding the {slug} URL patterns, though there are no parameters to clarify.

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 gives a specific verb ('List') and resource ('all published essays and fragments') and even enumerates the exact fields returned (titles, descriptions, prices, reading URLs), so an agent knows precisely what this produces. It does not explicitly name or differentiate itself from the sibling essay_payment_info, though the payment discussion gestures in that direction.

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?

It explains the two consumption paths (/read/{slug} for humans, /essays/{slug} paid via x402 for machine reads), which is genuine routing guidance for downstream reads. However, it never states when to call this tool versus the sibling essay_payment_info, so usage for the tool itself is only implied.

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