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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that by enumerating the returned fields (status, conclusion, branch, triggering event, links) and by advising where to source the owner, a real behavioral detail. No pagination/rate-limit or result-cap behavior beyond the schema's limit is described.

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 sentences, front-loaded with the purpose, then the parameter guidance, then usage triggers. Well ordered and free of padding, though the owner guidance mildly duplicates the schema.

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?

With no output schema, the description correctly compensates by sketching the return shape, and all five parameters are covered by the schema plus the description. A read-only list tool of this complexity is adequately described; only pagination/ordering behavior is unstated.

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 every parameter is already documented, making 3 the baseline. The description's owner/combined-form guidance largely restates the schema text for repo and owner rather than adding new semantics, though it does add the cross-tool provenance hint.

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 and resource ('List recent GitHub Actions workflow runs') with the scope qualifier 'for a repository', which separates it from the application-scoped sibling list_application_workflow_runs and the job-level get_workflow_run_jobs. An agent can place it correctly without opening any schema.

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 gives the situations to use it: 'check if CI/CD pipelines are passing, find failed builds, or monitor deployment workflows.' It also routes the agent to github_list_repositories for the owner value. It stops short of naming a true alternative or a when-not-to-use condition, so it is clear context rather than full routing.

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