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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the useful fact that the result feeds the org id into nearly every other tool. It says nothing about pagination behavior, though page_size/page_cursor exist, or about the shape of the returned list, so extra value beyond annotations is modest.

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, front-loaded sentences with the strongest guidance ('Call this FIRST') early. The trailing 'Forge v2: GET /orgs' is arguably noise for tool selection, but it does anchor the definition to a concrete API surface.

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 read-only, two-optional-parameter list tool with no output schema and full schema coverage, the definition covers what it returns and how to use it. The only real gap is pagination guidance for the two paging parameters, which the schema partially handles.

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?

Schema description coverage is 100%, so both parameters are fully documented in the schema, making 3 the baseline. The description adds nothing about pagination semantics such as when a cursor is needed or how large page_size may usefully be.

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 ('List organizations you belong to'), and adds scope ('you belong to') that distinguishes it from any general org-listing. No sibling covers organizations, so the agent can route unambiguously.

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?

Explicit sequencing guidance: 'Call this FIRST to get the organization id used by nearly every other tool,' which tells the agent both when and why to use it. No when-not condition or alternative is named, but for a prerequisite-listing tool the context is effectively covered.

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