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 the pagination mode ('offset pagination') and the underlying REST endpoint, which is mild but real context; however it says nothing about rate limits, default page size, total-count behavior, or auth requirements.

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, purpose first, pagination qualifier second, with no filler. The REST endpoint note is compact and useful to an API-aware agent rather than padding.

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 simple two-parameter read-only list tool with a fully documented schema and readOnlyHint annotations, the essentials are present. Still missing are the default/maximum effective page size behavior, whether the response includes pagination metadata, and how to narrow results — relevant since no filtering parameter exists.

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%: both 'page' and 'per_page' are documented in the schema, including the max-100 bound and exclusive minimum. The description's '(offset pagination)' merely corroborates the page parameter and adds no format or default details beyond the schema, 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 and resource ('List organizations') and notes the pagination style, which cleanly separates it from the sibling zendesk_get_organization (singular) without needing to name it. It doesn't explicitly differentiate itself in text, but the verb/resource pair is unambiguous.

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-to-use guidance, no mention of prerequisites or auth, and no routing to alternatives (e.g., zendesk_get_organization for a single org, or the fact that no org-search sibling exists). The agent must infer all usage context from the name alone.

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