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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the default sort order and the hint that related entities must be opted into via expand, which is genuinely useful, but says nothing about pagination limits (per_page max 50) or what happens when expand is omitted beyond the 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?

Three tight sentences, front-loaded with the resource and default order, followed by filtering and expand guidance. The trailing 'GET /customers.' earns little but is harmless endpoint context.

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 16-parameter list tool with no output schema, the description covers filtering and expansion but omits pagination behavior and anything about the response envelope (aside from the schema's next_page hint). Adequate but with clear gaps an agent would benefit from.

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 16 parameters including match semantics (partial vs exact) and sort syntax are already documented in the schema. The description's parameter mentions largely restate that surface, warranting the baseline 3.

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 ('customers') plus the default ordering ('newest id order unless sorted') and the filterable dimensions. This clearly separates it from the singular servicefusion_get_customer, though the description never names that sibling explicitly.

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 through the filter list and the 'add expand=... to include them' instruction, which tells the agent when to opt into extra data. However, there is no explicit when-to-use/when-not or routing to alternatives (e.g. get_customer for a single record), so the agent must infer selection.

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