get_report

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

With no annotations, the description discloses the response structure (status, counters, timestamps, price, per-recipient status) and pagination. However, it omits authorization requirements, rate limits, or error conditions.

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 paragraph that is moderately concise but includes some verbose phrasing like 'One response carries the overall order status'. It could be shortened without losing key information.

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 the tool's complexity (pagination, multiple response fields) and lack of output schema, the description provides sufficient context for an agent to use it effectively. It covers the main return fields and pagination mechanism.

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?

The input schema already describes parameters (id, page, rowCount) adequately. The tool description adds minimal extra meaning, only mentioning pagination, which is already in the schema. Baseline of 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 clearly identifies the tool as returning a delivery report for an order created via send-sms. It distinguishes itself from the sibling 'get_reports' by focusing on a single order and listing specific response fields.

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 implies usage after send-sms but does not explicitly state when to use this tool versus alternatives like 'get_reports' or 'cancel_order'. No exclusion criteria are provided.

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