ado_repositories_list

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add operational behavior instead: it discloses that the API returns a single unpaginated collection and that the response is capped at 4 MiB. That truncation/collection-shape detail is genuinely useful context an agent cannot get from the annotations.

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?

One sentence, front-loaded with the action and scope, with the parenthetical carrying two non-obvious operational facts. No filler.

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?

With a nested target object, zero schema descriptions, and no output schema, the definition leaves the agent without the structure of the required parameter or what a repository record contains. The 4 MiB note helps but does not compensate for the undocumented parameter shape.

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% and the single parameter is a nested object with five sub-fields (profile, project, repoPath, repository, organization), none documented anywhere. The description only obliquely hints that 'project' matters, leaving the agent to guess how to populate the rest.

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?

States a specific verb+resource ('List repositories') and adds scope ('in a project'), which is enough to distinguish it from siblings like ado_projects_list or ado_pipelines_list that target different resources. It does not explicitly name an alternative, but no sibling overlaps in resource.

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?

There is no guidance on when to call this versus other list tools, no prerequisites (auth/profile selection), and no note on whether a project is required or optional. The agent must infer usage entirely from the resource name.

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