List Azure DevOps projects

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it lists projects, but does not mention pagination via continuationToken, default page sizes, rate limits, authentication requirements, or whether the operation is read-only. The description offers minimal behavioral context beyond the bare function.

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, concise sentence that front-loads the core purpose. There is no redundancy or extraneous content. It is appropriately minimal for a straightforward list operation.

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 tool with three optional parameters, including a continuation token for pagination, the description is incomplete. It does not explain how to handle paginated results, what the default behavior is, or how stateFilter interacts with the results. Without an output schema, the agent lacks essential context about response format and iterative fetching. The description should at least hint at these aspects.

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 67% (top and continuationToken have descriptions; stateFilter does not). The description itself adds no parameter-level detail, relying entirely on the schema. Since the schema already documents two of three parameters adequately, the baseline of 3 applies, and the description contributes no additional semantic value.

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 ('List'), the resource ('projects'), and the scope ('configured Azure DevOps organization'). It is unambiguous and distinguishes itself from sibling tools that target other resources (pipelines, repositories, etc.).

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 explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of typical use cases, prerequisites, or exclusions. The agent must infer usage solely from the tool name and context, which is suboptimal for routing decisions.

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