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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally. The description adds value beyond that by explaining the semantic content of each returned item ('represents a deployment scenario'), which helps an agent decide whether the output is what it needs. No return format or pagination detail, but the list is presumably small and static.

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?

Three short sentences, zero waste, front-loaded with the action and followed by the definition and the routing cue. Every sentence earns its place.

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?

With no parameters, no output schema and complete annotation coverage, the description supplies what an agent needs: what the tool returns and why to call it first. It could go slightly further by naming the sibling tools it precedes, but it is functionally complete.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly avoids inventing filtering options.

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 states a specific verb and resource ('List available use-case profiles for BOM building') and clarifies what a use case is by giving concrete examples (campus access, data center top-of-rack). It does not explicitly name the sibling tools it complements, but the list/session/submit distinction is implicit in 'Start here'.

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?

'Start here to understand what kinds of BOMs you can build' gives clear entry-point context, implying this should be called before bom_start_session or bom_submit_input. No explicit when-not or alternative routing, but the sequencing guidance is unambiguous.

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