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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds essentially nothing beyond that: no pagination caps beyond the schema, no rate limits, no auth requirements, and no note that it returns a collection with paging metadata.

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 compact clauses, capability summary front-loaded before the REST endpoint reference. No filler, though the trailing endpoint line adds little decision value for an agent.

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 six-parameter read-only list tool with full schema coverage and no output schema, the description is minimally adequate: the schema carries parameter semantics and the annotation carries safety. However, nothing explains the returned shape/paging behavior or how this relates to sibling query/list tools, leaving a real gap.

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 the schema already documents page, sort, limit, where, expand, and search with examples and defaults. The description only echoes the capability names (filtering/sorting/search/expansion) and adds no syntax or constraint detail beyond the schema — 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 (List) and resource (orders) and enumerates the supported capabilities (filtering, sorting, search, expansion). It is clearly distinguishable from get_order/update_order, though it does not differentiate itself from the sibling list_* tools beyond the resource noun.

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 on when to use this versus alternatives like swell_query or swell_get_order, and no mention of prerequisites (auth, workspace scope) or exclusions. The only contextual hint is the raw REST endpoint, which is not usage direction.

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