delete_data_store

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

With no annotations, the description must carry the burden. It discloses that the tool deletes one or more data stores and returns a confirmation message, but omits consequences like cascading deletions, reversibility, or permission requirements. Basic information given, but significant gaps remain.

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 somewhat redundant: the first sentence 'Delete a data store' is repeated in the second paragraph 'This tool deletes one or more data stores'. The Args section largely repeats schema descriptions. While structured, it could be more concise.

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 tool's simplicity and full schema coverage, the description is adequate, but it does not address side effects, prerequisites, or what happens if both id and ids are provided (only schema notes this). The existence of an output schema reduces the need to explain return values, yet dependency handling is absent.

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 the schema already defines both parameters and their relationship. The description adds a helpful single-vs-batch explanation, but also lists 'ctx' as an argument that is not in the schema, which could confuse. Overall, minimal added value beyond the schema.

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 'Delete a data store from the architecture' with a specific verb and resource, and immediately distinguishes batch mode via 'ids' parameter. This differentiates it from sibling tools like delete_component or delete_connection.

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?

Provides explicit guidance for single-item vs batch usage: 'For single item: provide the id directly' and 'For batch: provide a list of IDs'. It does not explicitly exclude alternatives, but the tool's name and sibling set make the context clear. No misleading guidance.

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