Find GitHub Actions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond that: catalog size (75 actions), the existence of 3 eager daily drivers, and the fact that results include mutating flags plus complete parameter schemas for building the follow-up call.

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 sentences, zero waste, front-loaded with the core purpose and then the usage rule. The dense second sentence is entirely load-bearing (scope, trigger condition, examples, return shape).

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?

There is no output schema, but the description enumerates what is returned (action names, domain categories, mutating flags, descriptions, full parameter schemas), so an agent knows exactly what it gets back. Combined with the annotations, nothing needed to call this correctly is missing.

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 the schema already documents query, domain, and format in detail. The description restates the two filtering modes but adds no syntax, matching behavior, or edge-case guidance beyond what the enum and parameter descriptions provide; 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+resource ('Search and discover available GitHub actions in the 75-action catalog') with the two selection axes (keyword query or domain filter). It clearly distinguishes itself from the sibling github_execute_action by being the discovery step that feeds it.

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 says 'Use this discovery tool first whenever you need to perform an action outside the 3 eager daily drivers' and lists the domains that qualify (PRs, issues, releases, workflows, collaborators, webhooks, variables, security alerts). It also names the downstream tool to construct the call for, github_execute_action.

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