github_actions_delete_artifact

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether deletion is permanent, required permissions, or side effects like breaking workflows. The simple description is insufficient to inform the agent about the tool's behavior.

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 extremely concise (three words), which is efficient, but it sacrifices essential detail. It could easily include a sentence about the effect or requirements without becoming verbose. Thus, it is not optimally concise for effective tool selection.

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 absence of annotations and output schema, the description should provide more context about the tool's impact (e.g., 'This action permanently deletes the artifact and cannot be undone'). The current description is too minimal to be considered complete.

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%, but each parameter description is merely the parameter name (e.g., 'owner', 'repo', 'artifact_id'). The description adds no extra meaning beyond the schema. According to the guidelines, when coverage is high, baseline is 3, so this score is appropriate.

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 'Delete an artifact' clearly states the action (delete) and the resource (artifact). Combined with the tool name 'github_actions_delete_artifact', the purpose is unmistakable. However, it does not differentiate from other delete tools like 'github_actions_delete_actions_cache_by_id' or 'github_actions_delete_workflow_run'.

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 guidance is provided. The description does not indicate when to use this tool versus other delete tools, nor does it mention prerequisites, consequences, or alternatives.

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