list_task_runs

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

No annotations are provided, so the description must cover behavioral traits. It only states that the tool lists TaskRuns with certain fields. There is no mention of read-only nature, pagination, authorization, rate limits, or side effects. The description adds minimal behavioral context beyond what is assumed from the verb 'list'.

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 sentence that efficiently communicates the primary action and output fields. No extraneous words. It is front-loaded with the key information.

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?

Despite having an output schema (which may cover return values), the description lacks parameter explanations, usage context, and behavioral details. For a listing tool with three optional parameters, this is insufficient for an agent to use it effectively without further investigation.

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%, meaning the input schema provides no descriptions for the three parameters (cluster, namespace, label_selector). The tool description adds no information about these parameters, leaving the agent without guidance on their meaning or usage. This is a critical gap.

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 it lists Tekton TaskRuns and specifies output fields (task name, status, duration, age). The verb 'list' and resource 'Tekton TaskRuns' are specific, and it distinguishes from sibling tools like list_tasks (which likely lists Task definitions) and get_pipeline_run (which gets a specific run). However, no explicit differentiation is provided.

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 (e.g., list_tasks, get_pipeline_run). No prerequisites, filtering context, or conditions for use are mentioned. The purpose is implied but not explained.

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