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. "Return" weakly implies a read-only operation, but nothing is said about authentication requirements, scope of the contract, rate limits, or side effects. It adds almost no behavioral context.

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, so it is structurally tight. However, the brevity is a symptom of under-specification rather than disciplined concision, since no usable detail is conveyed.

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 documented. But with five undocumented optional parameters, no annotations, and no behavioral or usage detail, the definition is far too thin for an agent to invoke it confidently or distinguish it from its many siblings.

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 five filters (status, channel_id, artifact_id, endpoint_id, object_type_id), and the description explains none of them. It leaves the agent with no idea how these filters constrain or shape the returned contract.

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?

"Return the secure context evidence API and release contract" essentially restates the tool name (Secure Context Evidence Contract) with a generic verb. It does not distinguish, or even hint at the distinction, between this tool and the many sibling recipes_secure_context_* tools (attestation pack, lineage ledger, trust pack, value model, eval pack). An agent cannot infer what unique artifact this returns.

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 when-to-use guidance, no prerequisites, and no mention of alternative tools. With roughly ten closely named secure-context siblings, the absence of any routing signal is a serious gap.

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