cicd_github_workflow_runs

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only says 'list recent workflow runs' but does not explain pagination, rate limits, authentication requirements, what 'recent' means, or any side effects. The tag '[SAFE]' suggests non-destructive behavior, but that's minimal.

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 sentence that front-loads the main purpose. It is concise with no extraneous words. However, it could be slightly more structured with hints about parameters or usage.

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 the tool has 4 optional parameters, no output schema, and no annotations, the description is incomplete. It fails to explain what data is returned, how results are ordered, or any limitations like maximum results or time range. An agent would have to guess or use trial and error.

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%, so the description must compensate, but it does not mention any parameters. It provides zero clarification on what 'owner', 'repo', 'workflowId', or 'status' mean, nor does it explain the enum options for 'status'. The description adds no value over the raw schema.

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 exactly what the tool does: list recent workflow runs for a GitHub Actions workflow. It uses a specific verb 'list' and resource 'workflow runs', which clearly distinguishes it from siblings like 'cicd_github_workflows' (which likely lists workflows, not runs).

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention contexts or exclusions. It simply states the function without any usage direction.

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