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

Annotations already declare readOnlyHint=true, and the 'GET /api/integration/clients' line reinforces that this is a non-mutating read. The description adds little beyond that: no pagination behavior, no result-size limits, no note on default ordering. Adequate but thin for a tool with annotation coverage.

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, zero padding, and the resource description ('customers and organisations') is front-loaded. The raw endpoint path is marginally useful but borders on 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 fully documented optional params and no output schema, the description is minimally sufficient. However, an agent gets no picture of the response shape beyond 'contact details', nor of pagination defaults, which matters for a list endpoint.

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?

All three parameters (page, per_page, search_string) are fully documented in the schema at 100% coverage, so the schema carries the burden. The description adds no extra semantics such as what fields search_string matches against beyond 'contact details' being returned. 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 clients') and even disambiguates the resource as 'customers and organisations', which helps against siblings like list_passengers and list_users. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 statement of when to use this versus list_passengers, list_users, or list_subcontractors, and no guidance on when to paginate or when to supply search_string. The use case is only inferable from the name.

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