followupboss-mcp-server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a safe operation, what permissions are required, whether changes are reversible, what happens to unspecified fields, or what the response looks like. For a mutation tool with 10 parameters, 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?

While technically concise with just three words, this is under-specification rather than effective conciseness. The description fails to provide any meaningful information that would help an AI agent understand or use the tool correctly, making it inefficient despite its brevity.

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 mutation tool with 10 parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool does beyond the obvious, provides no behavioral context, offers no usage guidance, and fails to compensate for the lack of structured metadata about this potentially complex operation.

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%, so the input schema already documents all 10 parameters with basic descriptions. The description adds zero additional parameter information beyond what's in the schema, meeting the baseline score of 3 where the schema does the heavy lifting but the description doesn't enhance understanding.

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 'Update an appointment' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what aspects of an appointment can be updated or distinguish this tool from sibling tools like 'updateAppointmentOutcome' or 'updateAppointmentType' that handle related but different resources.

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's no mention of prerequisites (like needing an appointment ID), comparison to 'createAppointment' for new appointments, or when other update tools might be more appropriate for related entities.

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