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

With no annotations, the description carries the behavioral disclosure burden. The verb 'Return' conveys a read-only retrieval operation, which is useful, but nothing is said about authentication needs, scoping behavior, side effects, or what happens when filters are omitted. This is minimally adequate but not rich.

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. Every word contributes to identifying the resource and its scope, making it very efficient for an agent to parse.

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?

Despite having an output schema, the description omits key context: how the four optional parameters interact, whether filters are additive, what the default behavior is when all are null, and why an agent would choose this over siblings. The tool is simple on the surface, but the lack of filter semantics leaves meaningful gaps.

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%, so the description must compensate for the four undocumented parameters. It mentions content categories that loosely map to component types, but it never explains how namespace, agent_class, workflow_id, and component_type act as filters, how they combine, or what values they accept.

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 a precise resource ('Agentic System BOM'), and enumerates the content categories: workflows, agents, identities, MCP tools, and evidence. This clearly distinguishes it from the many sibling pack/risk/trust tools, which focus on different artifacts.

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 provided about when to use this tool versus alternatives such as recipes_agentic_posture_snapshot or recipes_agentic_exposure_graph. There are no stated conditions, prerequisites, or exclusions, so an agent must rely on the tool name alone to infer applicability.

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