list_trigger_templates

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

With no annotations, the description carries the behavioral disclosure burden. 'List' implies a read-only operation and the mention of template count and age gives some insight into what is returned. However, it does not explain scoping defaults, ordering, permission requirements, or whether the count/age is computed across the cluster or per namespace.

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 contains no filler and immediately names the resource and the notable output fields. It is appropriately sized for a simple 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?

The presence of an output schema reduces the need to describe return values, and the tool is a straightforward list operation. Still, the complete absence of usage guidance and parameter explanation leaves meaningful gaps for an agent deciding how to scope the call.

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 how 'cluster' or 'namespace' affect the results. While the parameter names are conventional, the description fails to compensate for the lack of schema documentation, leaving default behavior and filtering semantics unclear.

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 action ('List') and the specific resource ('Tekton TriggerTemplates'), and adds the computed fields 'template count and age'. It is not a tautology and is easy to distinguish from many siblings like list_tasks or list_pipelines, though it does not explicitly call out the closest alternatives.

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 about when to use this tool versus other Tekton-related listing tools, and no mention of prerequisites or whether cluster/namespace filters are needed. The intended context must be inferred entirely from the tool name and the single sentence.

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