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, and it discloses almost nothing. It clarifies only that templates are returned rather than persisted receipts, but says nothing about read-only vs. mutating behavior, side effects, auth/permission requirements, or idempotency. For a tool with zero annotation coverage this is a significant gap.

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 front-loaded sentence with no filler; the category list earns its place by scoping the returned templates. It is efficient, though the terseness comes at the cost of omitting any operational guidance.

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?

An output schema exists, so return values need not be explained, but the definition still leaves the agent without usage context, parameter meaning, or behavioral profile for a three-parameter tool. Given zero annotations and zero schema description coverage, the description is too thin to support confident invocation.

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% across three parameters (receipt_id, workflow_id, minimum_score), and the description does not mention any of them or explain filtering/scoring semantics. The enumerated categories (identity, context, tools, etc.) describe output content, not the input parameters, so the description fails to compensate for the coverage 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?

States a specific verb ('Return') and resource ('agent run receipt templates') and enumerates the receipt categories covered (identity, context, tools, egress, approval, evidence). It is clearly distinct from a generic template tool, though it does not explicitly differentiate itself from the closely related sibling recipes_agentic_approval_receipt_pack despite both touching 'approval' receipts.

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 on when to invoke this tool versus alternatives, nor any preconditions or context for its use. The agent must infer from the name alone that this is a template/artifact generator for agent run receipts.

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