list_agent_runs

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

Reveals ordering and pagination mechanism but does not state that the operation is read-only or disclose any side effects, auth requirements, or rate limits. Without annotations, the description provides moderate transparency but lacks completeness.

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?

Extremely concise: one sentence plus a clear bulleted argument list. Every sentence adds value with no redundancy.

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?

Covers core functionality and parameter details. With an output schema present, return value explanation is not needed. Minor omission: no mention of scoping (e.g., runs for a specific agent only is clear from agent_id). Adequate for a 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?

Adds significant meaning beyond the schema: explains agent_id with example, limit with valid range, and cursor origin. Schema has 0% description coverage, so the description fully compensates and clarifies each parameter's role.

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 tool lists runs for a Cloud Agent with explicit ordering (newest first) and provides the REST endpoint. It distinguishes itself from sibling tools like get_agent_run (single run) and create_agent_run (create).

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 vs alternatives (e.g., get_agent_run, stream_agent_run) or when not to use it. The description is purely functional without usage context.

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