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

No annotations are provided, so the description carries the full behavioral burden. It discloses a maximum of 50 results, which is useful, but it does not state that the operation is read-only, whether results are ordered by recency, how pagination works, or what happens when a pipeline has more than 50 runs.

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 short sentence with zero wasted words, and the key resource and result cap are front-loaded. It is appropriately sized for a simple two-parameter listing tool.

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?

With no annotations, no output schema, and zero schema description coverage, the description is too thin to fully specify the tool. An agent does not learn ordering, pagination, whether the limit default of 10 is respected, or any behavioral guarantees, which matters even for a simple list operation.

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 description coverage is 0%, and the description does not explain pipeline_id's role or the limit parameter's default of 10. The 'max 50' phrase adds some meaning, but it is ambiguous whether that cap applies to the limit value or the total number of runs returned.

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 states a specific resource and action: fetching recent runs for a pipeline, with a cap of 50. It is distinguishable from pipeline_run_get, which presumably fetches a single run, but it does not explicitly name that sibling or clarify that this is a list operation.

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?

There is no guidance on when to use this tool versus pipeline_run_get, pipeline_run_wait, pipeline_history_list, or pipeline_list. The phrase 'Recent runs' implies a listing use case, but selection criteria and exclusions are left entirely to inference.

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