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

Annotations already declare that the tool is read-only, idempotent, non-destructive, and closed-world. The description adds useful context that results include each series' product page and documents, but it does not describe pagination, result limits, or default behavior when no filters are provided.

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 two sentences and front-loads the core purpose and filters. The second sentence efficiently covers the return payload, with no wasted prose.

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 read-only lookup tool with fully documented parameters and no output schema, the description gives adequate context about filters and returned content. It could be more complete by explaining result limits, pagination, or the behavior of an empty query.

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%, so the parameters are already well documented. The description reinforces example values for chemistry, voltage, and application but does not add syntax or behavior 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 names a specific verb and resource: find a stationary battery or product series offered by Action Battery Wholesalers. It clearly scopes the lookup by chemistry, voltage, and application, but does not explicitly distinguish this from the sibling `search` tool.

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?

Usage is implied by the listed filter dimensions, so an agent can infer that this tool is for attribute-based series lookup. However, there is no explicit when-to-use/when-not-to-use guidance and no comparison to `search` or `fetch`.

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