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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says the tool 'returns' data, giving no information about side effects, safety, permissions, computation, or output behavior beyond the literal retrieval claim.

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 short and front-loaded with the verb, which is structurally clean. However, its terseness sacrifices substantive information, and the enumerated items are too generic to earn their place meaningfully.

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 and reduces the need to describe return values, but the description still lacks parameter semantics, usage context, and differentiation from siblings. With four opaque optional parameters and no annotations, the definition is not complete enough for confident tool selection and 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%, and the description does not explain any of the four parameters (decision, source_id, trust_tier, workflow_id) or map them to the output categories. This leaves the agent without any semantic guidance for invoking the tool correctly.

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 states a specific verb ('Return') and names a concrete resource: context provenance, retrieval policy, source hashes, and workflow context packages. However, among dozens of similar sibling recipe packs, it does not differentiate this trust pack from closely related tools like recipes_secure_context_attestation_pack or recipes_secure_context_lineage_ledger.

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?

The description provides no guidance on when to use this tool, what conditions favor it, or how it differs from sibling tools. An agent has no basis for choosing this over the many other secure-context and trust-pack tools.

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