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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the meaningful scope constraint that results are limited to "this connection," but it says nothing about pagination behavior, result ordering, or the size of returns, which matters for a listing 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?

A single sentence with no filler, and the primary mode (list organizations) is front-loaded ahead of the narrower modes. It is efficient if slightly dense, packing three distinct behaviors into one clause.

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 three-parameter read tool with no output schema, the definition is minimally sufficient but leaves real questions open: how the target organization is identified for the members and invitations modes, what fields are returned, and how pagination defaults behave. Annotations cover the safety profile but not these operational details.

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?

With 0% schema description coverage the description must carry the load; it does explain the semantics of the three action values, which is genuine added meaning over a bare enum. However, limit and offset are never mentioned, and the description says results are for "one" organization while the schema offers no parameter to identify that organization — a gap neither field explains.

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?

The description pairs a specific verb ("List") with a specific resource ("organizations") and names the three result sets it can produce (organizations, members, pending invitations). It is clear what the tool returns, though it does not distinguish itself from siblings such as list_datasets or get_api_keys beyond the resource noun.

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?

Usage is only implied through the enumeration of the three modes; there is no statement of when to choose members versus invitations, no prerequisites, and no named alternative for adjacent needs. An agent can infer the mapping from mode to result, but nothing more is offered.

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