list_pipeline_runs

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

No annotations provided, so description must disclose behavioral traits. It only says 'list recent runs' without mentioning pagination, read-only nature, or that results are limited. Lacks transparency on important behaviors like filtering and sorting.

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 sentence, highly concise and front-loaded. However, it is perhaps too brief given the tool's complexity. Could include a bit more context without sacrificing conciseness.

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?

Tool has 10 parameters, no output schema, and no annotations. Description is minimal but covers basic purpose. However, it leaves gaps: does not explain return format or pagination behavior. Adequate but not complete for an agent.

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?

Parameter descriptions in schema are comprehensive (100% coverage). The description adds no extra meaning beyond what schema already provides. Baseline of 3 is appropriate since schema covers semantics.

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?

Description clearly states 'List recent runs for a pipeline', which is a specific verb-resource combination. It distinguishes from sibling tools like 'get_pipeline_run' (single run) and 'trigger_pipeline' (create run).

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 on when to use this tool versus alternatives. Does not mention context, prerequisites, or when not to use it. The description is purely declarative without usage advice.

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