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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds non-obvious behavior: results are scoped to the credential's read permissions and one entry is flagged as the default, which explains why other tools may report no default. Return shape details and ordering are not described.

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 sentences, no filler. The purpose comes first and the usage routing follows, which is the right order for a discovery-style tool.

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-param, read-only listing tool with no output schema, the description covers what an agent needs: when to invoke it and how to use the result. It stops short of explaining how the default is marked or what fields an entry contains, leaving the agent to inspect the response.

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 goes slightly further by naming `org` as the identifier field that later tools consume, giving the agent the linkage between this call's output and downstream invocations.

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 ("Lists the organizations") and narrows the scope to those "this credential can read," plus a distinguishing output trait (the default is marked). No sibling tool touches organizations, so the resource alone separates it cleanly.

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 explicit trigger conditions ("Call it first when the user names an organization, or when another tool answers that no default is set") and the follow-up contract ("pass that organization's slug as `org` on every later call"). Both when-to-call and what-to-do-next are spelled out.

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