azdo_list_organizations

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

No annotations are provided, so the description carries full burden. 'List organizations' implies a read-only operation but doesn't disclose behavioral traits like authentication requirements, rate limits, pagination, or what the output looks like. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 'List organizations' is extremely concise with just two words, front-loading the essential information with zero waste. It's appropriately sized for a simple tool, though this conciseness comes at the cost of detail in other dimensions.

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 no annotations, no output schema, and a simple but vague description, the description is incomplete. It doesn't explain what 'organizations' means in this context (e.g., Azure DevOps organizations), what the return format is, or any behavioral aspects. For a tool in a server with many sibling tools, more context is needed to understand its role.

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 has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it doesn't contradict the schema. A baseline of 4 is appropriate for a zero-parameter tool where the schema coverage is complete.

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 'List organizations' clearly states the action (list) and resource (organizations), but it's vague about scope and doesn't differentiate from sibling tools like 'azdo_list_projects' or 'azdo_list_teams'. It provides basic purpose but lacks specificity about what kind of organizations are being listed or in what context.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'azdo_list_projects' and 'azdo_list_teams' that also list resources, there's no indication of when this tool is appropriate versus those, nor any prerequisites or contextual constraints mentioned.

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