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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a non-mutating read operation, which is the primary behavioral trait. It does not mention error handling, return format, or side effects, but for a simple read tool this is a minimal yet acceptable disclosure.

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, efficient sentence with no redundancy. It front-loads the action and resource, making it easy to scan and understand. Every word 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 tool with one parameter and no output schema, the description is very sparse. It does not explain what a 'Capability Receipt' is, what 'provenance' refers to, or what the caller should expect from the response. The absence of context beyond the verb leaves the tool under-specified for an agent that needs to call it 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?

The schema description coverage is 0%, and the description does not mention the 'receipt_id' parameter at all. It adds no meaning beyond the schema's type declaration (string), failing to compensate for the coverage gap. The parameter name is self-explanatory, but the description provides no additional semantics.

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 clear verb ('Read') and a specific resource ('standardized Capability Receipt and provenance'), giving the tool a distinct purpose. However, it does not differentiate from siblings like me_get_request or me_status, which could also be read-like operations. The jargon 'Capability Receipt' is unexplained but still narrows the scope.

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 is given on when to use this tool versus its many me_* siblings. There is no mention of prerequisites, typical scenarios, or alternatives. The name implies receipt reading, but the description leaves usage context entirely to inference.

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