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

With no annotations, the description carries the full behavioral burden. It discloses the categories of information returned, which helps an agent understand the tool's scope, but it does not explicitly state that the operation is read-only, whether it has side effects, or how the response should be interpreted beyond the field list.

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?

The description is a single compact sentence with no wasted words. Its noun-phrase style is efficient but somewhat telegraphic, and it would benefit from a short verb phrase such as 'returns' to make the action explicit.

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 simple, zero-parameter informational tool with an output schema, the description covers the main content areas. However, terms like 'receipt' and 'responsibility boundary' remain undefined in the description, and the relationship to the sibling fetch tool is not addressed.

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 has zero parameters, so there is no parameter meaning to explain. The baseline for a zero-parameter tool is 4, and no schema gap exists that the description must compensate for.

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 identifies a specific information resource: operator identity, receipt public key, limits, and responsibility boundary. It is clear enough to know what the tool is about, though it lacks a verb and does not distinguish itself explicitly from the sibling fetch tool.

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 no guidance on when to use this tool rather than fetch. It also does not state whether this is a static metadata lookup, when it should be called, or what conditions make it preferable to alternatives.

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