github_actions_delete_self_hosted_runner_from_repo

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

No annotations are present, so the description bears full responsibility for behavioral transparency. It only says 'Delete' without disclosing that the action is irreversible, may require admin permissions, or could affect workflow execution. The lack of such details is a significant gap for a destructive operation.

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 concise sentence that conveys the core action without extraneous information. It is appropriately brief for a simple deletion operation.

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 simplicity of the tool (3 required params, no output schema), the description is minimal but misses essential context such as the irreversible nature of deletion, required permissions, and post-deletion effects. For a destructive action without annotation support, more completeness is needed.

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?

Although the schema has 100% description coverage, each parameter description is just the parameter name (e.g., 'owner', 'repo', 'runner_id'). The tool description adds no additional meaning, such as the format of runner_id (presumably a numeric ID) or how to obtain it. The schema-level trivial descriptions do not compensate for the lack of enrichment.

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 clearly states the verb (Delete), resource (self-hosted runner), and scope (from a repository). It distinguishes from the sibling 'delete_self_hosted_runner_from_org' by specifying the repo context. However, it is generic and lacks additional context about what a self-hosted runner is.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives (e.g., deleting from an org), nor does it specify prerequisites such as the runner being offline or required permissions. This leaves the agent without guidance on appropriate invocation context.

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