ado_pipelines_get_logs

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

Annotations already indicate this is a read-only operation, and the description adds meaningful behavioral details: output is truncated to 10 KB to prevent context overflow and the tool requires the vso.build PAT scope. It does not cover empty results or pagination, but the key behavioral traits are disclosed.

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 compact and front-loaded with the core purpose, then adds return behavior and authentication needs. Every sentence contributes a distinct and useful piece of information without repeating schema fields.

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 simple two-parameter input, read-only annotations, and no output schema, the description covers the return shape, the 10 KB truncation, what to do to get full log content, and the required token scope. It is largely complete, though it does not explain how to obtain a relevant buildId when not already known.

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 the schema already documents both project and buildId. The description adds the pipeline-run context but does not provide additional parameter meaning, format details, or guidance beyond what the schema already gives.

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 a specific action and resource: getting build log references for an Azure DevOps pipeline run. It also tells the agent the result shape (list of log entries with id, type, url, lineCount) and distinguishes this from sibling tools like ado_pipelines_get_run or ado_pipelines_trigger.

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 explains what the tool returns and instructs the agent to follow each log URL for full content, which is useful. However, it does not explicitly say when to choose this tool over related pipeline tools or when not to use it, leaving most selection guidance implicit.

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