Execute GitHub Action

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description goes well beyond that by disclosing output post-processing (token projection filters, stripped URL templates/avatars/node_ids, compact Markdown default) and the read-only gating of mutating actions, which annotations do not convey.

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 dense sentences, front-loaded with the core verb+resource and the prerequisite before moving to output and gating behavior. Every sentence carries information, though the middle sentence packs many compression details into one run-on clause.

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 usefully explains the return format and projection behavior, and it covers the input prerequisite and mutation gating. It omits error/failure behavior and rate-limit or pagination handling, which would be needed for a 5 on a dispatcher of this breadth.

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 action, format, params, and parameters (including the alias). The description reinforces the exact-name requirement and the params dictionary but adds no format/syntax detail beyond what the schema provides, making the baseline 3 correct.

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 (Execute) and resource (GitHub action from the 83-action catalog), and notes it is name-driven with parameters. It partially differentiates from siblings by pointing at github_find_actions for name discovery, though it doesn't contrast with the other readers in the sibling set.

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?

Clearly states the precondition: the exact action name must first be discovered via github_find_actions, and flags that mutating actions are blocked under GITHUB_READ_ONLY=true. It gives no explicit 'when not to use' guidance or alternative for direct API-style calls, so it stops short of a 5.

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