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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Return ...' which implies a read operation, but it does not state whether results are filtered by the optional parameters, whether this is a safe read-only operation, what happens with null inputs, or whether any side effects or access requirements 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 a single, efficient sentence with no filler or repetition. It front-loads the action and the key output domains, though this brevity contributes to the lack of behavioral and usage detail.

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 presence of an output schema covers return-value structure, but the description still lacks usage guidance, behavioral context, and parameter semantics. Given the large sibling set and the zero-coverage schema, the description is not complete enough for an agent to select and invoke this tool confidently.

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%, so the description must compensate for the five undocumented nullable parameters. The listed output categories loosely map to parameter names (source_id, reuse_class, stage_id, workflow_id), giving an indirect hint, but it never explicitly explains what each parameter does, how they combine, or what values are expected.

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 uses a specific verb ('Return') and names the resource and expected output categories: context lineage, reuse policy, stage requirements, hashes, and workflow envelopes. This is clear about what the tool does, though it does not explicitly differentiate it from the many secure_context sibling tools.

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 given about when to use this tool versus alternatives like recipes_secure_context_attestation_pack, recipes_secure_context_evidence_contract, or recipes_secure_context_trust_pack. There is no stated context, prerequisites, or exclusion criteria, leaving the agent to guess based on the name alone.

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