github_migrations_delete_archive_for_org

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

With no annotations, the description bears full burden of behavioral disclosure. It only states 'Delete' without indicating that the operation is permanent, irreversible, or requires admin permissions. No side effects or expected outcomes beyond deletion are described.

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 sentence with no unnecessary words. It is front-loaded with the action and resource, making it efficient for an agent to parse.

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 delete tool with two straightforward parameters, the description is minimally adequate. However, it lacks information on the operation's irreversibility or preconditions, which would improve completeness. Context signals (no output schema, simple params) lower the bar, but still room for improvement.

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% (both parameters have descriptions 'org' and 'migration_id'). The description does not add meaning beyond what the schema provides. Baseline 3 is appropriate as the semantics are clear but not enriched.

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' and the resource 'organization migration archive'. It effectively distinguishes from sibling tools like 'get_status', 'list', 'start', and 'delete_archive_for_authenticated_user' by specifying the org context.

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?

The description provides no guidance on when to use this tool versus alternatives, such as whether the archive must first be downloaded or if it should be deleted immediately after migration. No prerequisites or exclusions are mentioned.

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