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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by mentioning the signature-check omission. However, the phrase 'with stated limits' is ambiguous and does not specify what those limits are, reducing transparency. For a read-only tool, the description provides moderate extra behavioral context.

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 extremely concise at two sentences, each adding unique information: the first defines the action, the second adds a key limitation. No wasted words, and the most important information is front-loaded. Perfect conciseness for this purpose.

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 0% parameter schema coverage, the description should provide more context about the return format, parameter details, and the nature of 'stated limits.' It lacks explanation of what the tool returns (e.g., field names, structure) and what the receipt input should look like. The description is incomplete for an agent to use the tool effectively.

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% for the sole parameter 'receipt' (type object/string with no schema description). The description does not compensate at all—it gives no information about what the receipt parameter should contain, format, or constraints. Since the schema provides no details and the description omits parameter semantics entirely, this is a critical 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 clearly states the tool reads a receipt field by field, which is a specific verb+resource. It also differentiates from sibling tools like verify_receipt by noting it does not check the signature. However, the phrase 'with stated limits' is vague and could confuse an agent about what constraints apply.

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 explicitly says 'Does not check the signature,' informing the agent when not to use this tool (e.g., if signature verification is needed, use verify_receipt). It implies usage for reading fields without verification, though it does not name alternatives explicitly or provide when-to-use conditions beyond that.

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