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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing about whether the tool is read-only, whether it mutates state, what auth it requires, or what triggers it. "Return" weakly implies a read, but that is inference, not disclosure.

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 padding, so it is structurally clean. But its brevity reflects under-specification rather than disciplined conciseness, so it earns only the minimum-viable score.

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 relieves the description of explaining return values, but with zero annotations, 0% parameter coverage, and three ambiguous optional parameters, the description leaves far too much unresolved for an agent to 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% across three parameters (decision, namespace, candidate_id), and the description never references any of them. An agent cannot tell whether these are filters, selectors, or write targets, so the description fails to compensate for the documentation gap.

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 enumerates the artifact types produced (decisions, risk findings, gaps, promotion plans), which is more specific than a tautology. However, it does not distinguish this tool from the many near-identical siblings such as recipes_mcp_connector_trust_pack, recipes_mcp_risk_coverage_pack, or recipes_agentic_app_intake_pack, and "intake pack" remains jargon an agent cannot map to a distinct operation.

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 alternatives. With a sibling list containing several overlapping MCP connector packs, the absence of routing guidance is a real gap rather than a minor omission.

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