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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds critical context beyond annotations: the permission tier required (platform admins only) and the explicit exclusion of ordinary owners/admins. It doesn't cover pagination or rate limits, but the permission model disclosure is substantive for a read tool.

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?

Four compact sentences with zero filler. The critical access restriction is front-loaded, and the workflow instruction follows logically. Every sentence adds value.

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?

Despite having an output schema, the description adds the critical missing piece: who can call this and how the returned organization_id feeds subsequent tools. The only gap is that page/page_size behavior (pagination semantics) is not mentioned, 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?

Schema coverage is only 50% – page and page_size are undocumented in the schema. The description compensates by explaining the search dimension (organization name, active owner name, owner email) and the downstream use of organization_id. It does not explain page/page_size, keeping this from a 5.

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/search) and resource (organizations), and distinguishes itself from the many other list_* siblings by describing the search-by-owner capability. An agent can tell it apart from list_studies, list_participants, etc.

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?

Provides explicit access gating ('Platform admins only'), describes the workflow ('Ask the human which match to use, then supply organization_id on another tool'), and states who CANNOT use it ('Ordinary organization owners and admins cannot use this tool'). This is unusually thorough routing guidance.

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