Retry a scheduled issue run now

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

Annotations indicate mutation, but the description adds no behavioral details beyond the endpoint. It does not explain what happens upon retry, side effects, or required permissions beyond 'board_or_agent'.

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 short and front-loaded, but it is too brief, omitting important information. It is concise but not sufficiently informative.

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 mutation, output schema, nested objects, and requires authorization, the description is incomplete. It fails to explain outputs, effects, or constraints, forcing reliance on the tool name.

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?

The description does not describe any parameters. The schema has a 'body' with a minimal description, and the 'path.id' is undocumented. Schema coverage is 50%, but the description adds no value.

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 title and description clearly state the verb 'Retry' and the resource 'scheduled issue run', and the endpoint gives specific context. However, it does not elaborate on what a 'scheduled issue run' is or distinguish it from other retry-related tools like 'recovery_actions_resolve'.

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 guidance on when to use this vs alternatives, prerequisites, or conditions. The description only provides the endpoint and auth class, leaving the agent without decision context.

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