discover_all_repositories

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

Describes that it walks the working directory for git repositories with Azure DevOps remotes. No annotations are provided, so the description carries the full burden. It does not disclose potential performance implications or side effects, but it adequately conveys the scanning behavior.

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 concise with two paragraphs and an Args list. Every sentence adds value, no redundancy. It is well-structured and front-loaded with the main action.

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 the presence of an output schema and the tool's simplicity (single optional parameter), the description is complete. It covers what the tool does, when to use it, and the parameter semantics.

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 coverage is 0%, but the description provides a clear explanation for the only parameter 'working_directory': 'Path to scan. Defaults to the current working directory when omitted.' This adds significant context beyond the schema.

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?

Clearly states 'List every Azure DevOps repository discovered under the working directory.' The verb 'list' and resource 'Azure DevOps repositories' are specific. The description also distinguishes from sibling tools by specifying use in multi-repo ambiguity error scenarios.

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 says 'Use this tool when another tool surfaces a multi-repo ambiguity error to enumerate the candidate repos so an end user can disambiguate.' Provides clear context for when to use, though does not explicitly mention when not to use.

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