seed_delete_org

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

With no annotations, the description carries the full burden. It discloses a key side effect (deleting the organization database file) and a permission requirement, which is valuable. However, it does not mention whether the operation cascades to related data (e.g., frames, tables) or whether it is reversible, leaving behavioral gaps for a destructive operation.

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 two sentences, front-loaded with the action, and every word adds value. It efficiently communicates the core function, side effect, and access requirement without redundancy.

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 one parameter and no output schema, the description covers the action, side effect, and permission. However, it omits details about the return value, behavior if the organization does not exist, and potential cascading effects on related resources, which would make it more 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?

The schema already fully describes the only parameter 'name' as 'Organization name to delete', giving 100% coverage. The description adds 'by name' but no extra semantic detail (e.g., case sensitivity, exact format), so it meets the baseline without exceeding it.

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 uses a specific verb ('Delete') and resource ('Seed organization'), and clarifies the scope by mentioning the organization database file. It clearly distinguishes from sibling tools like seed_delete_frames and seed_delete_views, which target other resources.

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 states a prerequisite ('Requires delete access') and implies the primary use case (deleting an org by name). It does not explicitly compare with alternatives, but since no other org-deletion sibling exists, this is clear enough context.

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