list_release_definitions

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

Annotations are absent, so the description carries the full burden. It only states the tool 'List's definitions, implying a read-only operation, but it does not disclose whether results are paginated, what the return format is, or whether any special permissions are required. Minimal additional context is provided.

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 unnecessary words. It is front-loaded with the action and resource, 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 lacks an output schema and annotations, and the description provides no usage context or behavioral details. For an agent deciding among many sibling tools, this description is insufficient. The three optional parameters are explained only in the schema, and no distinction from similar tools is made.

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?

The input schema covers all three parameters with descriptions, so schema coverage is 100%. The description itself adds no parameter-specific information, but the baseline of 3 is appropriate since the schema already handles semantic explanation.

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 'List release/deployment pipeline definitions' clearly states the action (List) and the resource (release/deployment pipeline definitions), distinguishing it from siblings like list_releases or list_pipelines by focusing on definitions. It is not fully specific about what constitutes a definition, but it is clear enough.

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 is provided on when to use this tool versus alternatives such as list_pipelines, list_releases, or get_pipeline_runs. The description does not mention filtering, prerequisites, or any context that would help an agent choose it appropriately.

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