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

Annotations already declare readOnlyHint=true, so the safety profile is covered, yet the description adds real behavioral value by stating sort order (newest first) and enumerating the returned fields (run id, status, conclusion, branch, commit, timing) — important since there is no output schema. It does not discuss rate limits or pagination edge behavior.

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?

Two compact sentences, front-loaded with the verb and resource and then the modifiers; nearly every clause carries information. The trailing 'Read-only' mildly duplicates the readOnlyHint annotation rather than adding new content.

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 read-only listing tool with no output schema, the description covers ordering, returned fields, filtering, and pagination — everything needed to call it correctly. Minor omissions remain (e.g., whether a total count is returned), but the tool is simple enough that this is sufficient.

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 page, page_size, status, and application_id are already documented with defaults and min/max. The description only echoes 'optional status filter and pagination', adding no syntax or value hints beyond the schema, so the baseline 3 applies.

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?

States a specific verb (List) and resource (an Application's CI/CD workflow runs/builds) plus the default ordering (newest first), which is enough to separate it from repo-scoped siblings like github_list_workflow_runs. It never names an alternative explicitly, so sibling differentiation is achieved by scope wording rather than direct contrast.

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?

The description notes that the status filter and pagination are optional, but gives no guidance on when to reach for this tool versus get_application_workflow_run_jobs, github_list_workflow_runs, or watch_workflow_run. No prerequisites, exclusions, or selection conditions are stated.

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