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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious context: that per-organization deletion permission is surfaced in the response, and that the list is bounded by consent-screen selections so unlisted organizations are not silently reachable. It does not discuss caching or refresh of the list, which keeps it from a 5.

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 sentences, front-loaded with what is returned, then the propagation rule, then the remediation for a missing organization. Every sentence adds information the agent would otherwise have to guess at, and there is no filler.

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 discovery tool with an output schema already describing the return shape, this covers the remaining gaps: what the fields mean, how to propagate the id, and the consent-screen boundary. Nothing needed to call it correctly 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 and the schema has nothing to explain. The description's mention of organizationId is about how to consume the result in other tools, not a parameter of this one, which is helpful framing rather than parameter documentation.

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?

Names a specific verb and resource ('List the organizations this connection may act in') and goes on to enumerate exactly what each entry contains: id, name, timezone, the caller's role, and whether deletion is permitted. Nothing about the tool's scope is left ambiguous, and it is clearly distinct from the content/publishing 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?

Gives an explicit conditional rule for downstream use ('When there is more than one, pass the chosen id as organizationId to every other tool') and covers the failure path ('To reach an organization that is not listed, the user must reconnect and select it on the consent screen'). This tells the agent both when the tool matters and what to do when its output is insufficient.

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