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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only lookup, what the default filtering behavior is, or how results are returned. The only behavioral hint (includeEmpty) is in the schema, not the description.

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 extremely concise, with no wasted words. The examples are useful and front-loaded. It is a fragment rather than a full sentence, but for a simple lookup tool, it is efficient.

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?

For a simple reference tool with no output schema or annotations, the description is too sparse. It does not explicitly state what the tool returns overall or how it relates to the product configuration context, leaving the agent with incomplete information.

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 100% for both parameters, so the schema already documents them clearly. The description adds no parameter-specific meaning, though the examples imply what search values might look like, which is marginal value.

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 is a noun phrase 'Filter cleaning' with examples rather than a clear statement of action. It implies the tool retrieves filter cleaning systems, but does not explicitly say 'list' or 'get'. It distinguishes the subject from siblings through examples like 'manual, Jet Clean, automatic backflush'.

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 on when to use this tool instead of the many sibling get* tools, nor any prerequisites or exclusions. The description lacks any contextual usage cues, making it hard for an agent to know when to select it.

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