list_organizations

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

No annotations are provided, so the description must cover behavioral traits. It states that it lists organizations and identifies the default, which implies a read operation. However, it does not disclose details about authentication requirements, item limits, or the format of the response. For a simple list tool, this is minimally adequate but lacks depth.

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?

The description is a single sentence of 10 words, front-loading the key action. Every word is necessary, and there is no superfluous content. It is extremely concise and well-structured.

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?

Given the tool has no parameters, no output schema, and no annotations, the description is the sole source of information. It clearly states the tool's purpose and the additional detail about the default organization. While it could mention possible access restrictions or response structure, it is reasonably complete for a simple listing tool.

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?

There are no parameters, and the schema coverage is 100% (empty properties). The description adds meaning beyond the schema by clarifying that it lists organizations and specifically identifies the default organization, which is not obvious from the tool name alone.

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 clearly states the exact action: 'List configured Backlog organizations and identify the default organization.' It uses a specific verb ('List') and resource ('Backlog organizations'), with an additional detail about identifying the default, which distinguishes it from sibling tools that list other 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?

The description does not provide explicit guidance on when or when not to use this tool, nor does it mention alternatives. However, since there are no other sibling tools for listing organizations and the operation is straightforward, the lack of detailed usage guidelines is tolerable but still a gap.

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