trawl_pool_delete

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

With no annotations present, the description carries the full burden and does well: it explicitly discloses irreversibility ('Permanently') and that both the directory and the index are destroyed, plus the confirm safety gate. It stops short of describing side effects such as whether search results, graphs, or memory entries tied to the pool are also affected.

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?

Two short sentences with zero filler; the destructive nature and scope come first and the safety prerequisite second. Every sentence earns its place.

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 two-parameter destructive tool with no output schema and no annotations, the description covers what an agent most needs: that it is irreversible, what gets removed, and that confirm must be set. Minor gaps remain around error behavior when the pool does not exist and permissions required.

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%, so both parameters are already documented in the schema, including 'confirm: Must be true to actually delete.' The description only restates the confirm requirement and adds nothing about pool_name semantics (e.g., whether the name must exactly match an existing directory). 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?

States a specific verb and resource ('Permanently delete a Trawl pool') and clarifies the scope of what is removed ('directory + index'). This clearly separates it from sibling pool tools such as trawl_list_pools, trawl_get_pool, and trawl_load_pool.

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 gives a hard prerequisite ('Requires confirm=true'), which is genuinely useful usage guidance. It does not, however, say when this should be used versus alternatives (e.g., whether there is any non-destructive removal path or what to do before deleting), so guidance is implied rather than complete.

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