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

There are no annotations to signal read-only, destructive, or authentication behavior, so the description carries the full burden. 'Return' implies a read operation and lists three content categories, but it does not disclose potential side effects, permissions needed, or whether a 'pack' artifact is generated or simply retrieved.

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, front-loaded sentence with no filler or redundant phrases. It is concise, though it achieves that brevity by omitting much needed context.

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 structure need not be restated, but the tool has five undocumented optional parameters and no usage guidance. The description names the result categories but does not explain how the filter parameters relate to those categories or when this tool is the appropriate choice, making the definition incomplete for correct invocation in ambiguous cases.

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 none of the five optional parameters (status, source_id, artifact_id, workflow_id, subject_type) are explained in the description. The description does not map any of the listed return topics to the input parameters, so an agent cannot determine how filters affect results.

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 identifies a distinct resource: secure-context attestation subjects, verification policy, and recertification state. This distinguishes it from some siblings by topic, but it does not explicitly differentiate from related secure-context recipe tools such as recipes_secure_context_trust_pack or recipes_secure_context_evidence_contract.

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 gives no guidance on when to use this tool rather than any of its many secure-context sibling tools. No context, alternatives, or exclusions are provided, leaving the agent to infer appropriateness from the name alone.

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