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

No annotations are provided, so the description carries the full behavioral burden. 'Read' weakly implies a non-mutating lookup and 'per-tenant scoped' hints at isolation, but nothing is said about what a missing receipt returns, error behavior, or how the identity is computed.

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?

A single compact sentence with the read action and scoping front-loaded. It is efficient, though it is terse to the point of under-specification rather than wasteful.

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 annotations, no output schema, 0% parameter coverage, and a nested args object, the description leaves too much unspecified for an agent to invoke this correctly. It should at minimum define the receipt concept and the three inputs.

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?

All three parameters (tool, args, scope_fields) have 0% schema description coverage, and the description does not explain any of them. 'Semantic identity' and 'per-tenant scoped' loosely gesture at scope_fields but give no format or expected values, especially problematic given the nested 'args' object.

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 read operation on a stored 'claim/receipt' keyed by a semantic identity, which conveys a rough purpose. However, 'claim/receipt' is never defined and the description gives no way to distinguish this from siblings dedup_execute, dedup_resolve, or guard_census.

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?

There is no statement of when to use this tool versus the sibling dedup_execute or dedup_resolve, nor any prerequisite or exclusion. The agent must infer usage entirely from the name.

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