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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds a genuinely useful behavioral caveat beyond that — "This connection only covers the organizations listed" — signalling that absence from the result is not proof of non-existence and depends on OAuth grants. It says nothing about ordering, pagination, or result size, though an output schema exists to carry return shape.

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 sentences, front-loaded with the action, then the purpose, then the scoping caveat and remediation. Every sentence carries information an agent needs. The final sentence is a little long and mixes agent instruction into the definition, but it is not padding.

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 an output schema present, return values need no explanation, and zero parameters means no input semantics to cover. The description supplies the two non-obvious things an agent needs: the connection's visibility limit and the reconnect remediation when an organization is missing. What remains unstated — result ordering and whether the list can be stale — is minor for a membership enumeration call.

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 add. Baseline 4 applies; there is no gap the description could have filled.

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 opens with a specific verb and resource ("List the Flagbearer organizations you belong to") and clarifies scope as membership-scoped rather than global. It also states the primary downstream purpose ("find an organization's ID"), which lets an agent place it relative to the list_applications/list_flags siblings. It stops short of explicitly naming a sibling it replaces or contrasts with.

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?

Guidance is clear: "Start here to find an organization's ID" establishes this as the entry point before other calls. It also defines an explicit failure path — if the project's application isn't among the returned organizations, tell the user and ask them to reconnect and approve the right organization before writing flag code. No explicit when-not-to-use or named alternative tool, which keeps it below a 5.

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