pbs_datastore_delete

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

With no annotations, the description fully discloses the mutation nature, dry-run default, conditional risk levels, async execution, and recovery path. It does not cover authorization or rate limits, but the core behavioral traits are well communicated.

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 well-structured with bullet points and front-loaded with key information. Every sentence serves a purpose, though there is minor redundancy in explaining dry-run both explicitly and via confirm parameter. Still, it is efficient and scannable.

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 output schema exists, the description appropriately omits return value details. It covers risk, async behavior, recovery, and provides a smoke-confirm hint. It lacks error scenarios or prerequisites, but overall is sufficient for agent understanding.

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%, so baseline is 3. The description adds significant value by explaining the risk implications of destroy_data and the role of confirm for execution, going beyond the schema defaults. It also clarifies the async outcome and recovery for destroy_data=False.

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 'PBS datastore', distinguishes from siblings by being the delete operation, and outlines the conditional risk and dry-run default.

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 clear context on when to use the tool with dry-run vs actual delete, explains recovery from non-destructive detach, and mentions async behavior. However, it does not explicitly state when NOT to use it or provide direct comparisons with alternatives like pbs_datastore_update.

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