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. It states a destructive action ('Remove'), implying mutation, but doesn't disclose behavioral traits like whether removal is permanent, if it requires specific permissions, what happens to conversation history, or if there are rate limits. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero waste—every word contributes to the core purpose. It's front-loaded and appropriately sized for a simple tool, avoiding unnecessary elaboration.

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 tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral context (e.g., permissions, reversibility), output expectations, and usage guidelines. For a destructive operation, this leaves critical gaps for an AI agent to invoke 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?

Schema description coverage is 100%, with clear parameter descriptions in the schema. The description adds no additional meaning beyond implying the parameters are used for removal. It doesn't explain format constraints (e.g., conversationId structure) or side effects, so it meets the baseline for high schema coverage without compensating further.

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 clearly states the action ('Remove') and target ('a participant from an inbox app conversation'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'deletePerson' or 'deleteGroup' by specifying the inbox app context. However, it doesn't explicitly differentiate from 'inboxAppDeactivate' or 'inboxAppUpdateConversation', which could involve participant changes.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing conversationId and personId), nor does it clarify if this is for active conversations only or if there are restrictions on who can be removed. The description assumes context without stating it.

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