Ops MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a list of repositories with specific fields (name, default branch, size, URL), which is useful behavioral context. However, it doesn't mention potential limitations like pagination, rate limits, authentication needs, or error conditions, leaving gaps for a tool with no annotation coverage.

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 well-structured and front-loaded with the core purpose, followed by usage guidelines, parameter details, and return information. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 1 parameter with no annotations but an output schema (which handles return values), the description is largely complete. It covers purpose, usage, parameter semantics, and return format. However, it lacks details on behavioral aspects like error handling or constraints, which would be beneficial since annotations are absent.

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?

The input schema has 1 parameter with 0% description coverage. The description adds meaningful semantics by explaining that 'project' is the 'Project name (default: Activate from config),' clarifying its purpose and default behavior. This compensates well for the low schema coverage, though it doesn't detail what 'Activate from config' entails.

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 specific action ('List all Git repositories') and resource ('in the Azure DevOps project'), distinguishing it from sibling tools like browse_repo (which explores files) and other unrelated tools. It provides a complete picture of what the tool does.

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 explicitly states 'USE THIS TOOL when the user asks about repos, code repositories, or wants to browse source code in Azure DevOps / TFS,' providing clear when-to-use guidance. It also mentions an alternative tool ('Use browse_repo(repo_name='...') to explore a repo's files') for related but different tasks.

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