tealfabric_delete_document

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

With no annotations, the description must carry behavioral transparency; 'Delete' plainly indicates a destructive operation on the target file or directory. However, it does not disclose whether directory deletion is recursive, whether deletion is permanent/recoverable, or what happens on missing paths, which are material gaps for a delete tool.

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 one short sentence with no filler or repetition; it delivers the action and resource immediately. Every word 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 simple delete tool, the core purpose and parameters are covered, but the lack of annotations and output schema leaves important operational details unstated, especially the semantics of deleting a directory. The tool is minimally usable but not fully contextualized for an agent deciding whether deletion is safe or recursive.

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%, and the schema already documents path as the file/directory to delete and tenant_id as defaulting to the authenticated tenant. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 opens with an imperative verb and narrow resource: 'Delete a file or directory from Tealfabric documents storage.' It is specific about both action and target, and the deletion action is distinct from sibling document operations like upload, download, and move.

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 makes it clear that this tool is for removing files or directories from document storage, which is unambiguous against the sibling tools. It does not enumerate exclusions or alternatives, but no alternative deletion sibling exists, so the core usage context is sufficient.

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