customer_ordered_products

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

No annotations provided; description indicates read operation and pagination, but does not mention sorting, default limits, or response structure. Output schema exists, lessening burden, but more transparency on behavior is needed.

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?

Description is very concise: one-line purpose followed by a clear parameter list. Front-loaded and no wasted sentences.

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 existence of output schema, description covers essential aspects: purpose, identification alternatives, pagination. Lacks details on possible errors or defaults, but adequate for its simplicity.

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 0%, so description adds minimal but helpful semantics: 'Internal customer ID', 'alternative to customer_id', 'Page number', 'Results per page'. Could include format or constraints.

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?

Description clearly states 'Get a list of products that a specific customer has ordered', which is specific and distinguishes from generic product_list. However, no explicit differentiation from sibling order-related tools like order_list.

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?

Description implies alternatives for customer identification (customer_id vs email) and pagination parameters, but does not provide context for when to use this tool versus other tools like order_list or product_list.

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