pipelines_list_events

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

The description only notes the GET endpoint, aligning with the readOnlyHint annotation. No other behavioral traits (e.g., pagination, error handling) are disclosed beyond what annotations provide.

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 concise, providing the core action and endpoint in one sentence. However, it is overly minimal.

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 6 parameters (1 required) and an output schema, the description is significantly incomplete. It omits details on pagination, filtering parameters, and response structure, making it insufficient for correct agent selection.

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 50% (3 of 6 params lack descriptions in schema). The description does not describe any parameters or add meaning beyond the schema, failing to compensate for the 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 'List pipeline events' and provides the REST endpoint, making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like pipelines_list or pipelines_list_updates.

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 alternatives, such as pipelines_list_updates. Context and exclusions are absent.

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