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. It implies a read-only retrieval, but says nothing about permissions, filtering behavior of the four optional inputs, pagination, or whether the returned packages are snapshots or live data.

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, which is structurally sound. The problem is underspecification rather than verbosity — the sentence is too thin to anchor a four-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 shape need not be described. But with no annotations, 0% parameter coverage, and no usage guidance for a tool surrounded by near-identical siblings, the definition is not complete enough for 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 four parameters (decision, source_id, trust_tier, workflow_id), and the description does not explain any of them. At best, 'source hashes' and 'workflow context packages' loosely gesture at source_id and workflow_id, leaving decision and trust_tier entirely undefined.

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 verb ('Return') and lists the kinds of content produced: context provenance, retrieval policy, source hashes, and workflow context packages. However, the boundary against close siblings such as recipes_secure_context_attestation_pack, recipes_secure_context_lineage_ledger, and recipes_secure_context_evidence_contract is not drawn, so an agent cannot readily tell which pack to pick.

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?

There is no statement of when to use this tool, when not to, or which alternative to prefer among the many recipes_secure_context_* and recipes_*_pack siblings. Usage can only be inferred from the noun list in the description.

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