github_code_scanning_delete_analysis

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action without revealing that deletion may be irreversible, the need for confirm_delete when deleting the last analysis, or any other side effects (e.g., impact on alert history).

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?

Single sentence, no redundant information. However, it lacks structure (e.g., bullet points or sections) and could be expanded slightly to improve readability without becoming verbose.

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 deletion tool, critical context is missing: the confirm_delete parameter behavior, the fact that deleting the last analysis may cause loss of historical alert data, and the need for appropriate permissions. The schema provides some of this for confirm_delete, but the description itself is incomplete.

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 coverage is 100% with descriptions for all parameters. The description adds no additional meaning beyond the schema; baseline 3 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?

Description clearly states the action (delete), the resource (code scanning analysis), and the scope (from a repository). It is specific and directly describes what the tool does, distinguishing it from sibling deletion tools like 'github_code_scanning_delete_codeql_database'.

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 tool vs alternatives such as deleting a code scanning database. The description does not mention prerequisites, required permissions, or the confirm_delete parameter's role in preventing accidental data loss from deleting the last analysis.

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