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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds real context by specifying that only 'top-level' organizations come back and which fields are present, but it says nothing about pagination or whether the result is permission-scoped beyond site deployment rights.

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 short lines, front-loaded with the purpose, then the return shape, then the chaining instruction. The field list (id, name, slug, type) partially duplicates the output schema, but it is compact enough to justify itself as a quick orientation for the agent.

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 parameters, an existing output schema, and full annotation coverage, this description already carries what an agent needs: what is listed, what comes back, and how to use the result next. Only pagination/scale behavior is left implicit.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. Nothing misleading is asserted about inputs.

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?

Specific verb and resource ('List the organizations'), plus a scoping qualifier ('the user can deploy sites into') that separates it from list_sites, list_cloud_accounts, and the rest of the read siblings. An agent knows exactly what this returns without opening the 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?

Gives an explicit downstream use: 'Use the id as organization_id in deploy_site,' which tells the agent this is a prerequisite discovery call before deployment. It stops short of stating when not to call it (e.g., if an organization_id is already known), so it is not a full when/when-not/alternatives treatment.

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