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

With no annotations, the description carries the full behavioral disclosure burden, but it only states what is returned. It doesn't disclose side effects, authentication requirements, read-only nature, whether output is generated or static, or how filters affect behavior. 'Return' implies retrieval, but significant behavioral context is missing.

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. It communicates the tool's primary output types efficiently, though it gives up completeness for brevity.

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?

Given the tool has two mysterious optional parameters, no annotations, and many similar sibling packs, the description is too thin. It doesn't explain what an 'assurance pack' is, what the parameters control, or how the output relates to other recipes. An output schema exists, but the description alone doesn't let an agent confidently select and invoke this tool.

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 makes no mention of control_id or workflow_id. The parameter names are mildly self-explanatory, but the description adds no meaning about how they filter, how they combine, or what values are valid, so it fails to compensate for the schema's lack of descriptions.

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 clear verb ('Return') and specifies three concrete artifact types: enterprise assurance controls, workflow evidence, and AI/Agent BOM seed. This is clear enough to understand the tool's topic, though it doesn't explicitly distinguish from sibling pack tools with overlapping terms like 'BOM' or 'control plane'.

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?

No guidance is given about when to use this tool versus the many sibling pack tools. The description is purely declarative and never mentions alternatives or contextual signals that would help an agent decide between, say, recipes_agentic_assurance_pack and recipes_agentic_system_bom.

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