delete_shared_folder

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

No annotations are provided, so the description carries the full burden. It discloses that the tool deletes the folder and its contents (destructive behavior). However, it does not mention irreversibility, permissions, or return value beyond the existence of an output schema.

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 very short and to the point. It uses a clear structure with an Args section. No unnecessary words or repetition. However, it could be slightly more structured (e.g., bullet points) but is still efficiently written.

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 description covers the basic purpose and parameter. However, it lacks details about return values (despite an output schema existing), error conditions, or permissions. It is minimally adequate but could be more complete.

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 schema has 0% description coverage, so the description compensates by specifying 'Name of the shared folder to delete' for the 'name' parameter. This clarifies the parameter's purpose beyond the schema's type-only definition.

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 'Delete a shared folder (and its contents).' The verb 'Delete' and resource 'shared folder' are specific. It distinguishes from sibling tools like 'delete_item' (which likely deletes files/items within folders) and 'create_shared_folder'.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies use for deleting shared folders, but does not mention alternatives or prerequisites. Given siblings like 'delete_item', the agent might infer usage, but explicit guidelines are missing.

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