manage_pull_requests

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

With no annotations, the description must reveal behavioral traits, but it only lists action names. It doesn't specify which actions are read-only vs. mutating, whether operations are idempotent, permission requirements, side effects, or error conditions. This is a significant gap for an 18-parameter tool.

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?

Very short and front-loaded, but the list of actions takes up most of the space. It is concise but sacrifices important behavioral information. Every sentence earns its place, but the description could be restructured to include context without increasing length significantly.

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 high complexity (18 parameters, 12 actions) and no output schema, the description is incomplete. It lacks action-specific guidance, parameter groupings, and behavioral context. An agent would need to read the entire schema and infer usage, which is suboptimal.

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 100%, so baseline is 3. The description adds no extra meaning beyond the action list, which is already in the schema's action parameter description. The schema already explains each parameter well.

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 tool manages Azure DevOps pull requests and lists all actions. This differentiates it from sibling tools (e.g., manage_repos, manage_work_items) by resource. However, it doesn't explain what each action does beyond the action name, so some ambiguity remains.

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 on when to use this tool vs. alternatives, or when not to use it. The description only enumerates actions without hints about choosing the right action or typical usage patterns. This leaves the agent without decision support.

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