ado_projects_list

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds value by specifying the exact return fields, which is beyond what annotations provide. It does not mention pagination behavior or edge cases, but for a read-only list tool this is adequate.

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 with zero redundancy. The primary action and resource are front-loaded, followed by a usage directive and a concise list of return fields. Every sentence contributes meaning.

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 list operation with full schema coverage and annotations, the description covers purpose, usage context, and return fields. It does not mention authentication or error handling, but these are not expected for such a straightforward tool and are likely covered at the environment level.

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%, with both 'top' and 'skip' parameters clearly described in the schema. The description does not add extra parameter-level semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 verb 'List' and the resource 'projects in the Azure DevOps organization', and lists the returned fields (name, ID, description, state, url, lastUpdateTime). It is specific and distinguishable from sibling tools that operate on work items, pipelines, or git.

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?

Explicitly instructs to 'Use this first to discover available projects before using other tools', giving clear context for when to invoke it. It does not explicitly state when not to use it or mention alternatives, but the context implies it is the discovery entry point and other tools are for specific resources.

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