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

Annotations already declare readOnlyHint=true so the safety profile is covered; the description adds real value beyond that by disclosing result ordering ('oldest first'), the shape of returned records, and the underlying endpoint. It stops short of describing pagination defaults or how 'include' affects response size, which would have pushed it higher.

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 with the core purpose front-loaded and no filler; the endpoint reference is compact rather than verbose. This is cleanly written with nothing that feels wasted, though it is a fairly minimal statement overall.

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 compensates by naming returned fields and ordering, and it closes the sibling-routing gap via kayako_search. Minor gaps remain around pagination behavior and how include changes the payload, but nothing essential to invoking the tool correctly is missing.

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 limit, offset, and include are already documented with ranges and the expansion semantics of include. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 customer organizations') and enumerates the returned fields (name, domains, phone, custom fields) plus ordering ('oldest first'). It also distinguishes itself from kayako_search for lookup-by-name, so an agent can route without opening either schema.

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?

Explicitly names the alternative tool and the exact invocation needed to select it: kayako_search with resources=['ORGANIZATIONS'] for single-organization lookup. Combined with the bulk-list framing and ordering note, the when-to-use routing is unambiguous.

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