Mooring

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

No annotations provided, so description carries full burden. States 'recent' but lacks pagination details, rate limits, authentication requirements, or cache behavior. 'List' implies read-only but safety profile isn't explicit.

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?

Compact Args block format efficiently documents parameters. No wasted words. Slightly informal structure (Python docstring style) but appropriate for developer tooling.

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?

Has output schema so return values don't need description. However, lacks critical operational context like GitHub token requirements and pagination behavior for 'recent' runs given the parameter complexity.

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?

Excellent compensation for 0% schema coverage. Describes repo format constraint (owner/name) and marks workflow/status as optional. Minor gap: doesn't enumerate valid status values (success, failure, etc.).

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?

Clear specific verb 'List' and resource 'GitHub Actions workflow runs'. Distinct from siblings like gh_issues (issues), gh_pr_list (PRs), and repo_log (git history).

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?

No explicit when-to-use or when-not-to-use guidance. No comparison with alternatives or prerequisites mentioned (e.g., GitHub authentication requirements).

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