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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description's 'Read-only' sentence merely restates readOnlyHint and adds 'wallet-bound' as the only new behavioral context; nothing about auth expectations or error behavior.

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 short, front-loaded sentences with no filler; the operation and its read-only nature appear immediately. The closing 'Read-only' is redundant with annotations but costs little.

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, three undocumented parameters, and multiple view modes, the description should explain what each view returns and how session_id/access_token are obtained. It leaves the agent unable to predict the response shape for any view.

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 must carry the burden, yet access_token and session_id are entirely unexplained (no format, provenance, or scope). Only the view enum is partially mirrored via the listed targets, and even then the 'next_action' default semantics are not tied to the enum.

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+resource ('Read a wallet-bound session/workflow/receipt/action') and the view targets map onto the enum options. It distinguishes itself from write-oriented siblings (create_session, prepare_*), though it doesn't name any sibling explicitly.

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?

No guidance on when to choose this over siblings like assetfare_status or assetfare_manifest, nor any prerequisites beyond an implied token requirement. The description never explains what selects each 'view' target.

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