github_actions_delete_hosted_runner_for_org

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Delete', implying a destructive action, but does not disclose consequences (e.g., irreversibility), requirements (e.g., permissions), or side effects (e.g., on ongoing workflows).

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 immediately conveys the purpose. However, it could include more detail without becoming overly verbose, such as clarifying the scope or side effects.

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?

For a destructive operation, the description omits critical context: that deletion is permanent, any error conditions, expected response, and prerequisites like the runner being offline. Given no output schema or annotations, the description should provide these details.

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 input schema parameter descriptions are tautological (just parameter names), and the tool description adds no additional meaning. It does not explain what 'hosted_runner_id' represents or how to obtain it, failing to compensate for the schema's lack of useful descriptions.

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', the resource 'GitHub-hosted runner', and the scope 'for an organization'. This distinguishes it from sibling tools like create, update, get, and list operations.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as the runner needing to exist or being idle, nor any indication of when deletion is appropriate compared to other operations like updating or listing.

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