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

No annotations are provided, and the description does not disclose behavioral traits such as whether results are filtered by search, how includeEmpty affects output, or the data structure returned. The phrase 'Available power supplies' only hints at a read-only listing, but important behavior is left unstated.

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 words. The examples are useful and compact. However, it is so brief that it omits guidance that could fit without bloating the text.

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 output schema and no annotations, the description carries the burden of explaining what the tool returns and how behavior changes with parameters. It only provides a vague resource label and examples, leaving the return format and the effect of includeEmpty/search unclear.

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 descriptions already fully document both parameters ('Optional text filter' and 'If true, include terms with no published products'), so the description adds no extra parameter context. The examples indirectly inform search content but do not clarify parameter semantics beyond the schema.

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 'Available power supplies' with concrete examples (electric, compressed air, battery), making it clear the tool returns a list of power supply types. It lacks an explicit verb, but the tool name supplies that. It partially distinguishes from siblings like getPowerValues via examples, though not fully.

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 on when to use this tool versus alternatives such as getPowerValues or getMotorPowerValues. There are no exclusions, prerequisites, or context clues about typical usage scenarios.

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