List characteristics

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

The annotation already declares readOnlyHint=true, so the read-only nature is covered outside the description. The description adds 'paginated,' indicating that the returned data may span pages, which is a small behavioral insight. It does not explain clamping, auto-pagination limits, or response shape, but these are already represented in the schema.

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 short sentence: 'List product characteristics (paginated).' It front-loads the main verb and resource and adds only the important qualifier 'paginated' in parentheses. There is no filler content, and the structure stays optimally scannable for an agent.

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?

The tool has low complexity, a read-only annotation, and fully documented optional parameters, so the description does not need to explain mechanics in depth. It does not have an output schema and the description does not mention the return format or any ordering/sorting behavior. The tool is also vaguely comparable to similar sibling list tools, so a slightly richer contextual note would improve completeness.

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%, and each parameter has a meaningful description including defaults, ranges, and behavior of 'all'. The main description does not need to repeat parameter details because the schema carries that burden. For a fully self-documenting schema, the baseline 3 is appropriate.

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 the specific action 'List' and the specific resource 'product characteristics,' so the main function of the tool is clear. The parenthetical '(paginated)' adds a useful qualifier about list behavior. It does not explicitly call out differences from sibling list tools such as list_characteristic_groups or list_characteristic_colors, which prevents a 5.

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 phrase 'List product characteristics' implies a common use case: obtaining a paginated list of characteristic records. However, the description does not explicitly say when to use this tool instead of get_characteristic, list_characteristic_groups, or list_characteristic_colors. Sibling names provide context, but the description offers no direct 'when to use' guidance.

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