recent_runs

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

No annotations are provided, so the description carries the full behavioral burden. It adds one important safety note — returned GitHub text is untrusted — and 'List' implies read-only, but it omits permissions, rate limits, and pagination behavior. This is a useful partial disclosure, not a complete behavioral profile.

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?

The description is a single front-loaded sentence: the operation is stated first, followed by a semicolon-linked security note. Every clause earns its place, with no filler or repetition.

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?

An output schema exists, so return-value details are not required in the description. However, with no annotations, 0% parameter coverage, and sibling alternatives, the definition is only minimally complete: it omits parameter semantics and usage routing, relying on the schema and sibling names to fill those gaps.

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 0%: repo, limit, and branch have only titles and defaults. The description mentions none of them, so it does not compensate for the missing parameter documentation at all. An agent learns nothing about what the required repo value format is, what limit controls, or how branch filters results.

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 states a clear verb and resource: 'List recent workflow runs.' It distinguishes the broad purpose from more specific sibling tools only implicitly; it never names failing_jobs, job_log_tail, or mixed_outcome_workflows, so an agent must infer that this is the general list tool rather than the filtered variants.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. Three sibling tools exist for narrower queries, but the description gives no routing cue such as 'use this for all recent runs, not just failing ones.'

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