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

readOnlyHint=true already declares the safe read profile, so the description merely needs to add context. It adds the upstream endpoint (GET /api/v2/organizations), which corroborates the read semantics, but says nothing about pagination defaults (page/count), result limits, or the `linked` side-loading behavior implied by the include parameter.

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, front-loaded sentences with zero filler: the capability first, the endpoint reference second. Nothing is repeated or wasted.

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 list tool with no output schema, the description does not mention pagination behavior or the shape/side-loading of results, leaving the agent to infer from the schema. Adequate but with clear gaps for a listing 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?

Schema description coverage is 100%, so all six parameters are already documented in the schema. The description only echoes the name and labels filters and adds no syntax or behavioral detail (e.g., how `search` differs from `name`, or pagination defaults), so 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+resource ("List customer organizations") and adds the filterable dimensions (name, labels), so it is clearly distinguishable from deskpro_get_organization and deskpro_create_organization. It stops short of explicitly naming sibling tools or scoping against deskpro_list_people/list_agents, so it is clear but not differentiated from siblings.

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?

There is no when/when-not guidance and no mention of alternatives such as deskpro_search or deskpro_get_organization for single-record lookup. The filterable-by-name-or-labels clause hints at usage but does not tell the agent which tool to pick under which condition.

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