list_products

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuine behavioral context beyond that: the 'indexed is false until searchable evidence exists' clause explains a state transition the agent would otherwise have to infer from the data.

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, which is appropriate for a no-argument list tool. The trailing clause about 'indexed is false' is compressed to the point of mild ambiguity about which attribute is being described.

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 an output schema present, the description need not document return values, and annotations plus a zero-parameter schema leave little else to explain. What remains slightly thin is the meaning of 'configured' versus 'indexed' and any ordering or filtering of results, but the core is 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 no parameters, so there is nothing for the description to clarify; baseline 4 applies. Schema coverage is 100% with an empty properties object, confirming no hidden inputs.

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 and resource ('List ... BMC products') and adds a meaningful distinction between configured and indexed states. It does not name or contrast any sibling tool, but the resource (products) is disjoint from the sibling set (projects, docs, versions), so differentiation is largely inherent.

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?

The listing intent implies when to call it, and no sibling tool competes for the same resource, so the implied usage is reasonably unambiguous. However, there is no explicit statement of when to use this versus checking sync/update status, nor any prerequisite or exclusion.

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