github_actions_create_remove_token_for_repo

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

With no annotations, the description carries the full burden. It only says 'Create', which implies mutation, but does not disclose any side effects, permissions required, token lifetime, or that it invalidates existing tokens. Transparency is low.

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, but it is too minimal to be fully informative. It earns its place by stating the action, but lacks substance necessary for an agent.

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 simple create-token tool, the description is missing key context: what a remove token is used for (removing self-hosted runners), that it is typically used in runner cleanup, and how it differs from registration tokens. The agent may not infer purpose.

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?

Input schema has high coverage (100%) but each parameter description is just the name ('owner', 'repo'). The tool description adds no additional meaning beyond the schema, failing to explain what a remove token is or how parameters are used.

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 'create' and the resource 'remove token for a repository', which is specific and distinguishes it from the sibling tool for organizations (github_actions_create_remove_token_for_org). The scope is unambiguous.

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 (e.g., registration token, or when a remove token is needed). The description lacks context for appropriate usage.

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