followupboss-mcp-server

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

No annotations are provided, so the description carries full burden. 'Delete a pond' implies a destructive, irreversible mutation, which is useful, but it doesn't disclose behavioral traits like permission requirements, whether deletion is permanent, if it cascades to related data, error conditions, or rate limits. For a destructive 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 ('Delete a pond')—just three words. It's front-loaded with the core action and resource, with zero wasted words. This is appropriately sized for a simple tool, though the brevity contributes to gaps in other dimensions.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens upon deletion, potential side effects, error responses, or success indicators. The context signals show minimal complexity (1 parameter, no nested objects), but for a delete operation, more behavioral context is needed to be 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 input schema has 100% description coverage (the 'id' parameter is documented as 'Pond ID'), so the baseline is 3. The description doesn't add any parameter-specific details beyond what the schema provides, but since there's only one parameter and it's well-documented in the schema, the description doesn't need to compensate. A score of 4 reflects that the description is adequate given the minimal parameter complexity.

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 pond' clearly states the verb (delete) and resource (pond), making the purpose understandable. However, it's quite basic and doesn't differentiate from sibling tools like 'deletePerson' or 'deleteDeal' beyond specifying the resource type. It's not tautological but lacks specificity about what 'pond' represents in this context.

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. There's no mention of prerequisites (e.g., needing a pond ID), consequences of deletion, or when to choose this over other deletion tools like 'deletePond' vs 'updatePond' (which exists as a sibling). It simply states what it does without context.

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