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

No annotations exist, so the description carries the full burden and does add real value: it discloses the privacy level, the API-key auth requirement, the internal structure of the receipt (supplier claims vs automated verification vs buyer review), and a prompt-injection warning about untrusted text and links. It still omits what a missing/unauthorized receipt yields and whether reads are audited.

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?

Three short sentences, all load-bearing: access scope first, then data-structure semantics, then the security caveat. No filler or restatement of the title.

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?

Covers access, privacy and injection safety well, which matters for a tool returning untrusted external content with no annotations and no output schema. However, it leaves the single input parameter and the shape of the returned receipt (what fields exist, what 'separate' sections look like) unexplained.

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% and the single required parameter is submission_id, yet the description never explains it beyond the loose word 'submission'. It does not state that it is a UUID or that it selects which receipt is returned, leaving the agent to infer everything from the schema.

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 specific verb and resource ('Read private delivery evidence') and scopes it to the caller's own submission or owned task. It is distinguishable from save_delivery_receipt and get_supplier_evidence by the 'evidence'/'receipt' framing, but never names a sibling to contrast with.

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?

'for your submission or a task you own' clearly defines the access condition under which this tool applies, which is good usage context. It stops short of naming alternatives (e.g. when to use get_supplier_evidence or get_delivery_issues instead) or stating exclusions.

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