get_reports

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

Discloses returned fields (counters, timestamps, sender) and what is excluded (per-recipient breakdown). Mentions the 10-day gap limit and error code 458, plus pagination with fixed page size. No annotations exist, so description carries full burden; minor gap on sorting or rate 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?

Description is concise at 3 sentences, well-structured with purpose, contrast to sibling, use cases, and a reference link. No wasted words.

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?

Completes the picture by explaining output content, typical use cases, and an error condition, all without an output schema. Covers all necessary context for an agent to use the tool correctly.

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?

Input schema has detailed descriptions for all parameters (start, end, page), so baseline is 3. The description does not add new information beyond the 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 an aggregate summary list of all SMS orders within a date range, explicitly distinguishing it from the singular 'get-report' tool which provides per-recipient breakdown.

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?

Provides explicit contexts: dashboards, periodic analytics, and 'list orders from last week'. Also tells when not to use it (for per-recipient breakdown) and recommends the alternative 'get-report'.

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