learningsuite_delete_group

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

As a destructive tool with no annotations, the description carries the full burden of disclosing effects. 'Delete a group' omits whether deletion is permanent, cascades to memberships or courses, or requires special permissions, making it dangerously underspecified.

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, direct phrase with no unnecessary words, making it concise. However, it is so terse that it sacrifices critical information, though this is more of a completeness issue than a conciseness issue.

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 destructive nature of the tool and the lack of annotations or output schema, the description is incomplete. It fails to mention the consequences of deletion, leaving the agent without essential context for such a high-impact operation.

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 groupId described simply as 'Group ID'. The description adds no meaning beyond the schema, so the baseline of 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?

The description states the action (delete) and the resource (group), clearly distinguishing it from sibling tools like create_group and list_groups. However, it lacks any additional scope or context, so it is clear but minimal.

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, no mention of prerequisites, and no exclusions. It simply states the action without any contextual direction.

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