group.delete

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

With no annotations present, the description carries the full disclosure burden. It does add one genuinely non-obvious behavioral fact — that member profiles survive the deletion (no cascade) — which is exactly the kind of side-effect an agent needs. However, it omits irreversibility, required permissions, and any other consequences of removing the group.

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?

Two terse sentences with no filler; the destructive action is front-loaded and the important side-effect follows 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 zero-parameter delete tool with no annotations and no output schema, the description conveys the core action and the profile-preservation behavior but says nothing about reversibility, preconditions, or what is returned. It is minimally adequate rather than 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 zero parameters, so per the baseline there is nothing for the description to expand on and no coverage gap to compensate for. A 4 reflects that the empty schema is not a defect the description needs to fix.

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?

States a specific verb and resource ('Delete a group'), which is unambiguous and clearly distinct from the sibling group.list and group.create. It stops short of explicitly naming or contrasting those siblings, so it is clear rather than maximally differentiating.

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?

There is no when-to-use guidance, no prerequisites (e.g., whether the group must be empty), and no mention of alternatives such as group.list for inspecting before removal. The agent is left to infer all situational context.

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