get_pipelines

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

There are no annotations provided, so the description bears full responsibility. It offers no behavioral details beyond the generic 'list' action; the term 'recent' is ambiguous and no pagination, filtering, or scope information is 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 a single four-word sentence that is entirely free of redundancy and front-loads the action.

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 absence of parameters and presence of an output schema, the description is minimally adequate, but it lacks explicit differentiation from sibling tools and does not clarify the meaning of 'recent'.

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 tool has zero parameters, and the schema coverage is 100% (vacuous). The description doesn't need to explain parameters, so the baseline of 4 applies.

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 lists recent pipeline runs, using the specific verb 'list' and identifying the resource as 'pipeline runs'. This distinguishes it from sibling tools like get_pipeline, which likely fetches a single pipeline.

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 siblings like get_pipeline or get_pipeline_steps. The description does not mention alternatives or any criteria for selection.

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