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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the result is sorted by name, each entry carries orgId/name/role, and an empty list has a specific meaning. It stops short of any pagination or volume caveats, but for a small list this is solid.

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, each carrying distinct information: what is returned, how to use it before create_project, and what an empty result implies. The most decision-relevant content (call before create_project) is front-loaded.

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 zero-parameter, read-only list tool with no output schema, the description supplies the return shape, ordering, and the downstream workflow constraint. Nothing an agent needs to call or act on this tool 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?

The tool takes zero parameters, so the baseline is 4. The description's enumeration of returned fields (orgId, name, role) partly compensates for the absence of an output schema, giving the agent a sense of what it will receive.

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) and resource (organisations), plus the qualifying scope '(you are an owner or editor there)' and the ordering (sorted by name). An agent can immediately distinguish this from siblings like list_projects or get_group.

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 says to call it before create_project, tells the agent what to do when multiple orgs exist (ask the user, don't pick for them), and interprets the empty-list case as 'you cannot create projects'. This is textbook when-to-use and when-not-to-act guidance.

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