manage_repos

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

The description only says 'Manage' and lists actions, without disclosing whether each action is read-only or modifies state, or any potential side effects. No annotations provide additional context, so the agent has no behavioral guarantees.

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 purpose and lists actions. However, it compresses all information into one sentence without clear separation of action descriptions, which could be improved for readability.

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 tool has 12 parameters and no output schema, the description lacks crucial context such as return values, prerequisites, or detailed behavior for each action. The agent would need to infer most usage from the schema alone.

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 100% coverage with descriptions for all parameters. The description adds only a list of action names, which are already in the schema's action parameter description. Therefore, the description provides minimal added value 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?

The description explicitly states it manages Azure DevOps Git repositories and enumerates ten specific actions, distinguishing it clearly from sibling tools like manage_pipelines or manage_work_items which target different resources.

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?

No guidance is provided on when to use this tool versus alternatives, nor on how to choose among the listed actions. The agent must infer usage solely from the action names and parameter requirements.

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