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

The annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the description's job is incremental — and it delivers: it discloses the required p2p:read scope, the restriction that Services-only keys cannot read these records, the same-organization boundary, and an explicit list of side effects that will not occur. What is missing is any indication of return shape, size, or pagination for the evidence payload.

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, each front-loaded with its most decision-relevant clause: capability first, access requirement second, non-actions third. Nothing is padded or repeated, and the negative list is compact and informative rather than filler.

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 single-parameter read tool with no output schema, the access and safety picture is well covered. However, the description leaves unclear what an 'evidence' record and its 'direct saved relationships' actually contain, which is exactly the information an agent would need to decide between this and the other procurement read siblings.

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?

There is one required parameter, id, whose format is uuid but whose meaning is not documented in the schema (0% coverage). The description never states what the id identifies — a purchase order, an evidence record, or a related artifact — nor what happens if it belongs to another organization, so it does not compensate for the schema 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 opens with a specific verb and resource: 'Read existing same-organization procurement records and their direct saved relationships.' That is clear enough to act on, but it never says 'purchase order' — the resource named in the tool name and title — and does not distinguish this from sibling read tools such as procurement_invoice__evidence, procurement_artifact__get, or procurement_order__documents.

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?

Usage is only implied: the reader must infer that this tool is for retrieving already-saved evidence records. The prerequisites (p2p:read scope, non-Services key) and the negative list (no uploads, inference, approvals, or money movement) narrow the use case, but no sentence states when to choose this over the evidence/get/document siblings.

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