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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful context with "tenant-private" and "signed output manifest," but it does not explain access requirements, error behavior if the audit is incomplete, or return format details.

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 definition is a single front-loaded sentence with no filler. Every word contributes to identifying the resource and the completed-state constraint.

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?

The tool is simple, and annotations cover its read-only safety profile, but with no output schema the description should say more about what the "result" and "signed output manifest" contain or how they differ from a receipt. It also omits any routing guidance against similar sibling tools.

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 parameter, audit_id, with 0% schema description coverage and only a regex pattern. The description never mentions the parameter or clarifies that it identifies the audit whose result is being read, so it does little to compensate for the missing schema 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 gives a specific verb ("Read") and a specific resource ("completed tenant-private result and signed output manifest"), so the agent knows what is being fetched. However, it does not distinguish this from closely named siblings like get_audit_receipt, get_audit_status, or verify_audit_report, leaving some ambiguity about the exact artifact returned.

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 adjective "completed" implies this tool should be used only after an audit has finished, which is useful implied guidance. But the description never states when to prefer it over get_audit_status or get_audit_receipt, nor does it give explicit when-not conditions.

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