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 the description says nothing about permissions, scoping behavior, whether filters are conjunctive, or what happens when no filters are supplied — all undefined given four optional parameters.

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 filler. It is efficient, though terse enough that it could have spent a few more words on filtering and sibling differentiation at little cost.

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 described, but the description still omits critical context: no annotations covering safety/mutation semantics, no explanation of the four undocumented filter parameters, and no differentiation from the many related agentic-* tools.

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 four parameters (namespace, agent_class, workflow_id, component_type) are explained in the description. The listed entity types loosely hint at filter dimensions, but there is no indication of how each parameter narrows the BOM or how they combine.

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?

States a specific verb ("Return") and resource ("Agentic System BOM") and enumerates the covered entity types (workflows, agents, identities, MCP tools, evidence), which gives the agent a concrete picture of scope. However, it never differentiates itself from closely-named siblings like recipes_agentic_exposure_graph or recipes_agentic_posture_snapshot, and "BOM" remains domain jargon.

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 stated preconditions, and no mention of alternative tools despite a large set of overlapping agentic-* siblings. The agent must infer usage purely from the name and description.

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