list_completions

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

No annotations provided, so description carries full burden. States it's cheap and non-blocking, explains return shape (list of get_dispatch shape with finished_at, raw omitted). Could elaborate on any side effects or auth requirements.

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?

Three concise paragraphs, each sentence adds value. Front-loaded with purpose, no wasted words.

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?

Given 2 optional parameters, no output schema, and no annotations, description is fairly complete. Covers return shape, typical polling pattern, and limitation (raw omitted). Could mention pagination for limits.

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 coverage is 0%, but description adds meaning to parameters: since is a threshold for finished_at, limit defaults to 50. Explains usage patterns that go beyond schema structure.

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?

Clearly states it lists completed jobs filtered by finished_at > since, oldest first. Verb 'list' with resource 'completions' is specific and distinct from sibling tools like list_jobs or get_dispatch.

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?

Explicitly provides usage patterns: use since=0 for all completions, track largest finished_at for polling. Advises on caller frequency (start of every turn) and contrasts with get_dispatch for full payloads.

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