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

No annotations are provided, so the description carries the full burden, but it says nothing about read-only semantics, authorization requirements, pagination, or what scoping constraints apply. It only implies a read via 'Return', leaving the behavioral profile essentially undisclosed.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. But the terseness tips into under-specification rather than tight conciseness for a five-parameter tool.

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 with zero annotation coverage and five undocumented parameters the description is far too thin to let an agent invoke this correctly. It does not compensate for the structured-data gaps.

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?

All five parameters have 0% schema description coverage with no enums or required fields. The description's nouns (reuse policy, stage requirements, workflow envelopes) hint at reuse_class, stage_id, and workflow_id, but 'decision' and 'source_id' are unaddressed and no formats, defaults, or filtering semantics are explained.

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 verb ('Return') and a list of resources (lineage, reuse policy, stage requirements, hashes, workflow envelopes) are present, so the tool is identifiable as a ledger lookup. However, the payload terms are internal jargon and nothing distinguishes it from the many sibling 'secure_context'/'agentic' pack tools, so an agent cannot reliably tell it apart from neighbors.

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 when-to-use context, no prerequisites, and no named alternatives are given despite dozens of overlapping sibling tools. Usage is only implied by the retrieval verb.

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