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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is largely covered. The description does add scope constraints beyond the annotations: no guest identity, no merchant credentials, no financial action, and the note that repeat reads do not add earnings. That is real added context, though it stops short of describing pagination or return shape.

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?

Three sentences, front-loaded with the core read action and no obvious padding. The second sentence is cryptic but not verbose, and each sentence attempts to add a distinct constraint rather than repeat structured data.

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?

With no output schema and four fully undocumented parameters, the description would need to explain pagination, the cursor/limit relationship, and the event-sequence semantics. It covers none of these, and the follow-up-credential sentence raises more questions than it answers, leaving the agent without enough to invoke correctly.

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 0% across four parameters (limit, cursor, order_id, after_event_sequence), so the description carries the full burden. It mentions 'one inquiry and limited order projection,' which faintly gestures at order_id, but limit, cursor, and after_event_sequence are entirely unexplained. The description does not compensate for the coverage gap.

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 states a specific action and scope: reading the calling Agent's 'already accepted attribution/status/reward receipts.' However, the resource is described in dense internal jargon ('attribution/status/reward receipts', 'commerce progress') and it never uses a plain verb like 'list' or states what a receipt actually contains. It is interpretable but requires domain knowledge to distinguish from siblings.

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?

There is no guidance on when to use this tool versus alternatives such as evuun_get_commerce_capsule or evuun_list_service_inquiries. The sentence about a 'separate finite owner-approved follow-up credential' and 'its one inquiry and limited order projection' is opaque and does not translate into a usable when/when-not rule.

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