list_release_definitions

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

With no annotations, the description must disclose behavior fully. It mentions the tool lists definitions with a default project and top count, but omits details such as read-only nature, pagination behavior beyond the top parameter, required permissions, or any side effects. The output schema exists but the description does not highlight key behavioral traits.

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 two concise sentences followed by parameter definitions. Every part serves a purpose: the first sentence states the core operation, and the parameter list explains inputs. No redundant or extraneous text.

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 simplicity of the tool (list with two parameters) and the presence of an output schema, the description covers the basics. However, it lacks usage guidelines, behavioral transparency, and context about when to use this tool versus siblings. For a complete picture, it should mention that it lists only classic release definitions and any prerequisites.

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 coverage is 0%, so the description carries the burden for parameter meaning. It explains that 'project' is the Azure DevOps project name (uses default if not specified) and 'top' is the maximum number of definitions (default 50). This adds semantic value beyond the schema's defaults.

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 'List all classic release definitions (release pipelines) in a project.' It specifies the verb 'list', the resource 'release definitions', and the scope 'in a project', effectively differentiating it from sibling tools like 'list_releases' (which lists actual releases from those definitions).

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it differs from tools like 'get_release' or 'list_releases'. The agent receives no contextual cues for selection.

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