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

Beyond the readOnlyHint and idempotentHint annotations, the description adds meaningful behavior: it returns an embedded PDF resource, performs no side effects, and requires a completed record with specific verification data. This fully informs an agent about what will and will not happen when the tool is invoked.

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 dense, front-loaded sentences with no filler. The purpose, return type, side-effect absence, and prerequisite are all included without repetition or unnecessary detail.

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 two-parameter, read-only, idempotent tool with an output schema, the description covers the essential context: what it generates, what it returns, what it avoids, and when it is valid to call. Nothing critical for correct invocation is missing.

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 coverage is 0%, so the description carries the burden of explaining parameters. It indirectly describes kind via 'receipt or platform fee' and id via 'completed record with a recorded transaction and verification time', but it never explicitly names the id or kind parameters or maps them to schema properties. Partial compensation, but not complete.

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 names a specific action (generate), a resource (completed-payment receipt or platform fee PDF), and a mechanism (existing AurasPay renderer). It also clarifies what the tool does not do (email, payment, fee collection, notification, status change), which distinguishes it from siblings like auraspay_payment_create and auraspay_payment_get.

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 gives clear context: use it to produce a PDF receipt or fee document for a completed record, not to trigger payment or send email. It states a prerequisite (completed record with recorded transaction and verification time) and an explicit exclusion, though it does not name an alternative sibling for email or export workflows.

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