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

With no annotations, the description carries the full burden. It does disclose useful behavior beyond the schema: pagination is supported and the result set can be narrowed by status and date range. However, it says nothing about auth/permission requirements, the default ordering of results, or the shape of what is returned, which matters for a history endpoint with no output schema.

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 short sentences, front-loaded with the primary purpose and followed by capability summary. Every clause earns its place; no filler.

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 read-only list tool with 0 required params and no output schema, the description covers the filtering and paging surface adequately. Still missing is anything about result ordering, overall volume, or whether the resource requires an authenticated context, leaving modest gaps for an agent to call it confidently.

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 description coverage is 100%, so all five parameters (from, to, page, limit, status) are already documented with types, ISO 8601 hint, defaults and max. The description only restates the capability categories ('pagination, status filter, date range') without adding syntax or constraints beyond the schema, so the baseline of 3 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?

States a specific verb and resource ('List past SMS activation orders'), and the word 'past' implicitly separates it from the sibling list_active_orders. It stops short of explicitly naming or contrasting with that sibling, so an agent still has to infer the boundary.

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?

Usage is implied by 'past orders' plus the filter list, but there is no explicit when-to-use statement, no exclusion of active orders, and no pointer to list_active_orders or get_order as the alternative for a single order. The agent must infer selection from the name alone.

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