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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them: the fields the records contain, the fact that these are tracking records with no payment involved, and the pagination contract (meta.nextPageNo).

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?

Three short sentences, front-loaded with the resource and returned fields, then the disambiguating note, then the paging contract. The trailing "GET /orders" is mildly redundant but the rest is dense and waste-free.

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?

With no output schema, the description carries the burden of describing returns, and it does enumerate the record fields plus the paging meta field. It stops short of stating list size, default page size, or whether results are filterable, which would be needed for a fully complete picture.

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 page_no and per_page are fully documented in the schema, including the meta.nextPageNo handoff and per-page bounds. The description only echoes the paging behavior without adding format or constraint detail, so the baseline 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 order records") and enumerates the record fields returned, so the agent knows this is a collection read. It does not explicitly differentiate itself from the sibling get_order (single record) or create/update_order, leaving that inference to the agent.

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 the verb plus the paging instruction, and "no payment is involved" usefully clarifies what these MailBluster-side records are. However, there is no explicit when-to-use or when-not-to-use guidance, and no reference to get_order as the alternative for single-record retrieval.

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