delete_webi_doc

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the most critical trait, that deletion is permanent/irreversible ('Permanently deletes'), which is genuinely useful. It omits other important context such as authentication requirements and what happens to existing instances, schedules, or dependencies of the document.

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?

One efficient, front-loaded sentence with zero filler. It is arguably too terse for a destructive operation, but there is no wasted text.

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?

An output schema exists, so return values need not be explained, and the permanence of the operation is stated. However, for a destructive tool with no annotations and an undocumented identifier, the description is thin on prerequisites and side effects, leaving meaningful gaps for an agent.

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 0% and the description adds no meaning about webi_doc_id (format, where to obtain it, whether it is a CUID or numeric ID). With low coverage the description should compensate but does not, though the single-parameter surface limits the damage.

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?

Clear specific verb (deletes) plus resource (Web Intelligence document) and scope (from the repository). An agent knows exactly what is being removed. It does not, however, explicitly differentiate itself from siblings like delete_folder, delete_instance, or purge_dp, though the resource noun is fairly distinct.

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 when-to-use guidance, no prerequisites (e.g. required login/session state), and no alternatives named. The single sentence states the effect but leaves the agent to infer when this tool is the right choice versus delete_instance or purge_dp.

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