ado_list_organizations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it warns about credential limitations (organization-scoped PATs may not work) and mentions that results are filtered by an organization allowlist. This is useful operational behavior not visible in the schema.

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 sentences, each earning its place: the first states the action and scope, the second warns about credential compatibility, the third notes allowlist filtering. No filler or repetition of schema details.

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 simple read-only tool with one parameter and no output schema, the description covers the essential context: what it reads, for whom, credential caveats, and filtering behavior. It doesn't describe the return format, but with no output schema and a simple list operation, this is a minor gap.

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 0%, so the description must compensate. The description explains that memberId is an explicit member UUID and that the call reads accounts for that member, which adds meaning beyond the raw schema field. It doesn't detail the UUID format beyond the schema's format field, but for a single-parameter tool this is adequate.

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 action ('Read'), the resource ('Azure DevOps Accounts'), and the specific scope ('for an explicit member UUID using the Accounts API'). It also distinguishes itself from sibling tools by naming the API and the member-based scope, so an agent can tell it apart from ado_list_configured_organizations and ado_list_projects.

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 clear context: it reads accounts for a specific member UUID and notes credential requirements ('Requires compatible identity credentials/profile permissions; may not work with organization-scoped PATs'). It does not explicitly name alternative tools or state when not to use it, but the context is sufficient for an agent to infer appropriate use.

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