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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: results are scoped to caller membership and only 'active' projects are returned, which implies archived projects are excluded. It doesn't address empty-result or pagination behavior, but the output schema carries the 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?

Two sentences, zero filler, with the scope statement front-loaded and the critical 'call this first' instruction second. Every clause carries information an agent needs.

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 parameterless, read-only listing tool with an output schema and full annotation coverage, the description supplies exactly the missing pieces: what entities come back, that they are permission-scoped and active-only, and why the call must come first. Nothing required for correct invocation is absent.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The mention of which identifiers are returned compensates slightly by framing the output fields agents will consume downstream.

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 states a specific verb (list) and precise resources (organizations the caller belongs to plus the active projects accessible in them), resolving the ambiguity created by the name 'list_projects'. It is clearly distinguishable from singleton siblings like get_organization and get_project, and from list_members/list_clusters which return different entities.

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?

'Call this FIRST' with the reason (the returned (organizationId, projectId) pairs are required by every other tool) is an explicit, actionable sequencing rule that no sibling provides. It stops short of naming when-not-to-use or naming a named alternative, but for a zero-argument bootstrap tool that guidance is close to sufficient.

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