followupboss-mcp-server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a group' implies a destructive, irreversible mutation, but the description fails to specify whether this requires special permissions, what happens to associated data (e.g., members, content), whether deletion is permanent or recoverable, or any rate limits. For a destructive operation with zero annotation coverage, this is critically inadequate.

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—a single three-word phrase—with zero wasted words. It is front-loaded and gets straight to the point. While this conciseness comes at the expense of completeness, the structure itself is optimal for its limited content.

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 destructive mutation tool with no annotations and no output schema, the description is completely inadequate. It fails to address critical contextual elements: what deletion entails (permanent? cascading?), required permissions, error conditions, or what the tool returns. The agent lacks sufficient information to use this tool safely and effectively.

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 100% description coverage (the 'id' parameter is documented as 'Group ID'), so the schema does the heavy lifting. The description adds no additional parameter context beyond what's in the schema—it doesn't explain where to find the group ID, format requirements, or validation rules. With high schema coverage, the baseline score of 3 is appropriate.

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 a group' is a tautology that essentially restates the tool name. While it clearly indicates the action (delete) and resource (group), it provides no additional specificity about what constitutes a group, what deletion entails, or how this differs from similar deletion tools like deletePerson or deleteTeam. It meets the basic requirement of stating what the tool does but lacks differentiation 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 absolutely no guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., needing the group ID), consequences of deletion, or comparison to related tools like deleteTeam or updateGroup. The agent must infer usage entirely from the tool name and parameter schema.

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