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

The readOnlyHint annotation already establishes safety, and the description adds useful behavioral context by stating it 'Returns a paged collection' and identifies the underlying 'Ecwid REST: GET /orders.' This goes beyond the annotation by clarifying pagination behavior and the exact API method, though it does not discuss rate limits or auth.

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 three short sentences with no waste: it states the purpose, the filter categories, the paged return, and the REST endpoint. Key scoping information is front-loaded before the optional endpoint reference.

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 search tool with 10 optional parameters and a schema that documents every parameter, the description provides enough high-level context: filters, paged collection, and endpoint. It lacks explicit response-structure details, but since no output schema exists and all invocation parameters are documented, the definition is nearly complete.

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 has 100% description coverage for all 10 optional parameters, so the schema carries the parameter documentation burden. The description only summarizes filter categories without adding new semantic details, matching the baseline for high schema coverage.

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 a specific verb and resource: 'Search / list the store's orders' with optional filters. It conveys collection-level behavior via 'Returns a paged collection,' which implicitly separates it from single-order tools like ecwid_get_order, but it does not explicitly name or contrast any sibling.

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?

No guidance is given about when to use this tool versus alternatives such as ecwid_get_order, ecwid_search_customers, or ecwid_update_order. The description states what the tool does but does not provide when-to-use conditions, exclusions, or prerequisite context.

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