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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavior (results are ordered newest-first and enriched with per-status job counts), but says nothing about pagination despite exposing page_size, nor how many records a default call returns.

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 tight sentences, with the core operation and ordering front-loaded and filters following. The trailing 'Depot: CIService/ListWorkflows' is internal implementation noise that consumes space without helping an agent invoke the 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?

No output schema exists, so the description usefully pre-announces the shape of results (ordered, counted by status). However, for a 7-parameter paged listing tool it omits pagination/limit behavior and default ordering scope, leaving gaps an agent must probe at runtime.

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 100%, so the baseline is 3. The description loosely maps the filters ('name/path text', 'SHA prefix', 'PR number') but adds no semantics beyond the schema, and omits page_size entirely.

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?

Specific verb+resource ('List Depot CI workflows') with scope ('across runs'), ordering ('newest first'), and an enrichment detail ('per-status job counts'). The agent can distinguish this from the sibling depot_ci_list_runs, which lacks the workflow-level grouping and counts.

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?

It enumerates the filter dimensions available, which implies when the tool is useful (narrowing a workflow search), but never states when to prefer it over siblings like depot_ci_list_runs or depot_ci_get_run_status, and offers no exclusions or prerequisites.

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