delete_datasource_entry

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

The description does not disclose side effects (e.g., irreversibility, cascading effects on related data), permissions required, or error scenarios. For a delete operation, these are critical for safe invocation. With no annotations, the description carries the full burden, but it fails to provide necessary behavioral context.

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, clear sentence that contains all essential information without unnecessary words. It is front-loaded and efficient.

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?

While the tool has one parameter and no output schema, the description lacks behavioral details (permissions, irreversibility) that would contribute to completeness. In the context of many sibling tools, it does not provide differentiating context. Given the simplicity, it is minimally adequate.

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 single parameter 'datasource_entry_id' is described in the schema, and the description mentions 'datasource entry' which aligns. With 100% schema coverage, the description adds no new meaning beyond the schema. Baseline score of 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?

The description clearly states the action ('Deletes'), the resource ('datasource entry'), and the context ('Storyblok space using the Management API'). It effectively distinguishes from sibling tools like 'delete_datasource' and other delete operations.

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?

No guidance on when to use this tool versus alternatives (e.g., delete_datasource, bulk_delete_stories). It does not mention prerequisites, such as needing the datasource entry ID, or conditions under which deletion is appropriate. Without this, agents may misuse it.

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