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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds pagination scope (one page, up to 60) and filter semantics, but does not mention rate limits, auth needs, or result ordering behavior beyond sort names.

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?

Front-loaded with the core purpose and output shape, then flows into parameter guidance efficiently. Some field enumeration is dense but reasonable for a catalog search tool.

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?

Given 8 params, 100% schema coverage, output schema present, and readOnly/openWorld annotations, the description covers what an agent needs: scope, pagination, available filters, and the source of filter IDs. Nothing material is missing.

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 baseline is 3. The description goes a step beyond by clarifying that attr values must come from aliexpress_search_filters for the same q and that multiple values can be comma-separated (up to 5), which the schema also states; still useful cross-tool context.

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+resource (search AliExpress's keyword catalog) and enumerates the returned product fields, which no sibling does. Distinguishes itself from aliexpress_search_filters, which the description explicitly references as the source of attr values.

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?

Explains how to use q, page, sort, price filters, free_shipping, choice, and attr, and points to aliexpress_search_filters for attribute IDs. It gives clear usage context but does not exclude alternatives or state when to prefer other catalog tools.

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