Delete Sharing Group

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Permanently delete' reinforces and adds irreversibility nuance. However, it does not disclose side effects such as what happens to associated resources, permissions, or error behavior. The description adds some value beyond annotations but is not rich.

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 concise sentence ('Permanently delete a sharing group by id.') that is front-loaded with the action and contains zero waste. 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 with one parameter, no output schema, and annotations covering destructive/idempotent behavior, the description is sufficient. It fully conveys the operation. It could optionally mention how to obtain the group_id (e.g., via list_groups) but this is not essential for such a straightforward tool.

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 coverage is 100% with the parameter group_id described as 'Sharing group id'. The description's 'by id' adds no new meaning beyond the schema. Baseline 3 is appropriate since the schema fully documents the 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 clearly states the action: 'Permanently delete a sharing group by id.' The verb 'delete' and resource 'sharing group' are specific, and the tool is distinct from sibling tools like lyzr_sharing_create_group, lyzr_sharing_update_group, and lyzr_sharing_list_groups. It fully clarifies what the tool does.

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?

Although no explicit alternatives are named, the description implies clear usage: use when you need to permanently remove a sharing group. The tool name and sibling context make the purpose obvious, providing clear context without exclusions. Not a 5 because it lacks an explicit 'use X instead' statement.

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