list_pipeline_variables

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 mentions the return format ('List of pipeline variables with key, secured status, and value'), which adds some context. However, it lacks critical details like whether this is a read-only operation, if it requires authentication, pagination behavior beyond the 'limit' parameter, or error conditions. For a list operation with zero annotation coverage, this is insufficient.

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 well-structured and front-loaded with the core purpose, followed by parameter and return details. Every sentence earns its place: the first states the action, the 'Args' section clarifies inputs, and the 'Returns' section explains outputs. It's appropriately sized with zero waste.

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 tool's moderate complexity (2 parameters, no annotations, no output schema), the description covers the basics: purpose, parameters, and return format. However, it lacks behavioral context (e.g., safety, pagination) and doesn't reference sibling tools. For a list operation, this is adequate but leaves gaps that could hinder agent effectiveness.

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 description includes an 'Args' section that documents both parameters ('repo_slug' and 'limit') with brief explanations, adding meaning beyond the input schema (which has 0% description coverage). However, it doesn't elaborate on format (e.g., what a 'repository slug' is) or constraints (e.g., 'limit' range). With schema coverage low, the description compensates partially but not fully.

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 the tool's purpose: 'List pipeline variables for a repository.' It specifies the verb ('List') and resource ('pipeline variables') with scope ('for a repository'), making it unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_pipeline_variable' (singular) or 'create_pipeline_variable', though the plural vs. singular naming provides implicit distinction.

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 doesn't mention sibling tools like 'get_pipeline_variable' (for a single variable) or 'create_pipeline_variable', nor does it specify prerequisites or contextual constraints. The agent must infer usage from the name and description alone.

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