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. 'Create a pond' implies a write operation but reveals nothing about permissions, side effects, error conditions, or what happens upon success. For a mutation tool with zero annotation coverage, this is completely inadequate—it doesn't even hint at the tool's impact or requirements.

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?

While concise with only two words, this is under-specification rather than effective brevity. The description is front-loaded but fails to provide any useful information—it's so minimal that it doesn't earn its place. True conciseness balances brevity with utility, which is absent here.

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 that this is a mutation tool with no annotations, no output schema, and a sparse description, the description is severely incomplete. It doesn't explain what 'creating a pond' entails, what the result might be, or any behavioral context. For a tool that presumably modifies system state, this leaves critical gaps for an agent trying to use it correctly.

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 description adds no parameter information beyond what the schema provides. However, schema description coverage is 100% (the single parameter 'name' is documented as 'Pond name'), so the baseline score of 3 applies. The description doesn't compensate for any gaps, but none exist in the schema documentation.

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 'Create a pond' is a tautology that merely restates the tool name. It specifies the verb ('create') and resource ('pond'), but lacks any differentiation from sibling tools like 'createPerson' or 'createDeal', which follow the same pattern. While it states what the tool does at a basic level, it doesn't provide meaningful specificity beyond the obvious.

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 are no mentions of prerequisites, context, or exclusions. With sibling tools like 'updatePond' and 'deletePond' available, the description fails to help an agent understand when creation is appropriate versus modification or deletion.

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