dev_pipeline_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and a closed world, so the safety profile is covered. The description adds one real behavioral fact beyond the annotations – ordering is newest-first – but says nothing about pagination, how many runs exist, or what a 'persistent' run is.

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?

A single compact sentence with the ordering constraint front-loaded and no wasted words. Efficient, though the brevity is partly achieved by omitting needed content rather than by tight editing.

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?

For a list tool with no output schema, the description carries no information about filtering parameters, result shape, or default limits despite three undocumented parameters. An agent has to guess how deviceId/deviceName narrow the list.

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% for three parameters (limit, deviceId, deviceName), and the description mentions none of them. It does not explain that results can be scoped by device or capped by limit, so it fails to compensate for the documentation 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?

Clear verb+resource: 'List persistent pipeline runs.' An agent can distinguish this from dev_pipeline_status (single run) and dev_pipeline_logs without opening a schema. However, 'persistent' is ambiguous and no sibling is named explicitly, so it stops short of a 5.

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 statement of when to use this versus dev_pipeline_status, dev_pipeline_logs, or dev_pipeline_wait, nor any prerequisites. Usage context is left entirely to inference from the name.

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