ado_pull_request_changes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that the operation is a read/list, but adds no details about pagination, authentication, scoping, or what exactly counts as a 'changed file'. The description does not go beyond the basic operation.

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 with no filler. The verb and object are front-loaded, and every word earns its place.

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?

The tool is simple, and an output schema exists, so return-value details need not be in the description. However, with no annotations and no usage or parameter guidance, the description is minimally complete rather than fully contextualized for an agent choosing among related pull request tools.

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 description does not explain any of the parameters. The parameter names and titles are fairly self-explanatory, but the description does not compensate for the lack of schema-level descriptions, such as clarifying the optional project field or how pull_request_id relates to the repository.

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 uses a specific verb and resource: 'List changed files for a pull request.' This clearly distinguishes it from sibling tools like ado_pull_request_get, which retrieves pull request details, and ado_pull_requests_list, which lists pull requests.

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 makes the core use case clear—use this when you need the files changed by a pull request—but it does not explicitly state when not to use it or name alternatives. The usage context is implied rather than explicitly contrasted with sibling tools.

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