delete_share_folder__id_

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Delete folder share' implies a destructive operation, but it fails to specify permissions required, whether the deletion is reversible, what happens to associated data, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with just three words, front-loading the core action and resource. There is no wasted verbiage or redundancy, making it efficient in terms of brevity, though this conciseness comes at the cost of completeness.

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 complexity (a destructive operation with 1 parameter), lack of annotations, 0% schema description coverage, and no output schema, the description is severely inadequate. It fails to provide necessary context such as parameter meaning, behavioral details, or usage guidelines, leaving the agent ill-equipped to use the tool correctly.

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 input schema has 1 parameter ('id') with 0% description coverage, meaning the schema provides no semantic information. The description does not mention parameters at all, offering no compensation for the lack of schema documentation. This leaves the agent guessing about the meaning and format of the 'id' parameter.

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 'Delete folder share' restates the tool name with minimal elaboration. It specifies the action (delete) and resource (folder share), which is better than a tautology, but lacks specificity about what a 'folder share' entails or how it differs from similar tools like 'delete_folders_folder'. The purpose is clear at a basic level but not well-differentiated from siblings.

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 provides no guidance on when to use this tool versus alternatives. With multiple delete-related tools in the sibling list (e.g., 'delete_folders_folder', 'delete_workspaces__wid__profiles'), there is no indication of context, prerequisites, or exclusions. This leaves the agent without direction on appropriate usage scenarios.

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