get_orders_summary

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

Annotations declare readOnlyHint=true. Description adds transparency about partial aggregation (partial:true if window exceeds max_pages×100) and exact count. Could mention more about performance or limits.

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?

Single sentence with parenthetical clarification is efficient and front-loaded. Every word adds value; no redundancy.

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?

Describes key return fields and partial flag, but without output schema, it lacks detail on edge cases (e.g., empty result, structure of status distribution). Could be more thorough.

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 covers 100% of parameters. Description adds context about computed fields (revenue, AOV, status distribution) and how max_pages affects aggregation window, filling gaps not in 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 clearly states the tool returns a period-scoped order summary with specific metrics (totalCount, revenue, average order value, status distribution). It distinguishes from siblings like list_orders and get_customers_summary.

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 use for aggregated summaries vs. individual order views, but no explicit guidance or alternatives are mentioned. Could specify when to use over list_orders or get_customers_summary.

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