ado_pipeline_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no mention of pagination, auth/profile requirements, error behavior for missing pipeline IDs, or what the read actually returns.

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?

Single short sentence with zero waste and front-loaded verb+resource, but the brevity comes from omission rather than efficiency — there is no useful detail to be concise about.

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?

With a nested target object, 0% schema coverage, and no output schema, the description should explain what the target fields are for and what the returned definition contains. It provides none of that, so an agent must guess how to construct the target object.

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 target parameter is a nested object with five sub-fields (profile, project, repoPath, repository, organization) whose meaning and selection rules are entirely undocumented. The description mentions no parameters at all, leaving both pipelineId and the target object unexplained.

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?

States a specific verb (Read) and resource (pipeline definition), which is enough to separate it from ado_pipelines_list and ado_pipeline_run_get at a coarse level. However, it doesn't articulate what part of the definition is returned or how it differs meaningfully from listing pipelines.

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?

There is no explicit guidance on when to use this vs. ado_pipelines_list or ado_pipeline_run_get; the agent must infer that this fetches one definition by ID. No prerequisites or exclusions are mentioned.

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