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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states that the tool returns content. It does not reveal whether this is a pure read operation, whether it depends on external systems, whether it enforces approval workflows, or what side effects—if any—exist.

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 description is very concise and front-loaded, with no filler words. However, the brevity sacrifices necessary detail, making it under-specification rather than effective conciseness.

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?

Despite having an output schema, the description is insufficient for an agent to safely and correctly invoke the tool: parameter semantics are absent, no usage context is given, and there is no explanation of what 'scope-bound' means. The combination of five undocumented parameters and no annotations leaves a substantial gap.

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?

The input schema has five parameters with zero description coverage, and the description does not explain `decision`, `risk_tier`, `workflow_id`, or `action_class`. 'Scope-bound' is too vague to compensate for the complete absence of parameter 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 names a specific verb ('Return') and a resource ('scope-bound approval receipt profiles, workflow requirements, and evidence'), so the core purpose is somewhat clear. It does not explicitly distinguish itself from sibling tools like recipes_agentic_run_receipt_pack, but the approval-receipt focus separates it enough to avoid complete ambiguity.

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 is provided about when to use this tool instead of the many similar sibling 'pack' tools. 'Scope-bound' hints at a scoping mechanism but does not explain what scope means or how it relates to the parameters.

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