Get Bulk Commissions

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

Annotations already provide readOnlyHint and openWorldHint, so the description carries low burden. It adds that the tool returns 'commissions and possible reductions' but omits details like response structure, performance, or side effects. No contradictions.

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?

Two sentences, no redundant words. The purpose and required inputs are conveyed efficiently. Ideal length for a straightforward 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?

For a simple bulk retrieval tool with one well-defined array parameter, the description covers the core use case. Lack of output schema is mitigated by mentioning return type (commissions and reductions). Minor gap: no details on rate calculation logic.

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 coverage is 100%, so the description repeats parameter info (EAN, unit price, condition) already in the schema. It adds no significant new meaning beyond the structured fields. Baseline score applies.

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 clearly states the verb 'Get' and the resource 'commissions and possible reductions' for multiple products in bulk, distinguishing it from single-product 'get_commission' and rate-focused 'get_commission_rates'.

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 description tells users to provide EAN, unit price, and optionally condition, but does not explicitly state when to use this bulk tool versus alternatives like 'get_commission' for single products. The context is implied but not explicit.

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