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

Annotations declare readOnlyHint=true, so the safety profile is already known. The description adds valuable behavioral context beyond the annotation: it clarifies that the tool returns both the signed event and the current resource state, and it explicitly warns that a receipt signature does not verify truth or ownership. This is meaningful behavioral disclosure that helps an agent set expectations.

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, no wasted words. The core action is front-loaded, and the critical caveat about signature verification is placed at the end where it is easy to notice. Every sentence 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 single-parameter read tool with readOnlyHint=true, the description is mostly complete. However, it does not clarify what the 'id' refers to, what the return format looks like, or how this relates to the sibling read_* tools. The caveat is useful but leaves the agent to infer the exact input semantics.

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%, so the description carries the burden for parameter semantics. The description mentions 'portable signed event' and 'current resource state' but does not explain what the 'id' parameter refers to (e.g., event ID, receipt ID, or resource ID). With only one parameter, the baseline is 4, but the lack of any parameter-specific detail in the description reduces it to 3.

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 verb ('Read') and resource ('portable signed event') and adds that it 'separately returned current resource state', which distinguishes it from a plain event read. It doesn't explicitly name a sibling alternative, but the phrase 'portable signed event' and the caveat about receipt signatures help differentiate it from other read_* tools.

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 context: it is for reading a portable signed event and its current resource state. However, it does not explicitly state when to use this tool versus alternatives like read_interaction, read_ledger, or get_events. The caveat about receipt signatures hints at a verification use case but does not provide explicit when/when-not guidance.

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