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. It fails to describe any behavioral traits such as whether this is a read-only operation, if it requires authentication, what the return format looks like (e.g., list structure, pagination), or any rate limits. The description is too minimal to inform the agent about how the tool behaves.

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 just three words, the description is under-specified rather than efficiently informative. It lacks necessary details about the tool's behavior, output, or usage context, making it ineffective despite its brevity. Conciseness should not come at the cost of clarity.

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 zero parameters and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'list' entails (e.g., returns all outcomes, supports filtering, includes metadata), leaving the agent with insufficient information to understand the tool's functionality and expected results.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is acceptable given the lack of parameters. A baseline score of 4 is appropriate as the schema fully covers the parameter aspect.

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 'List appointment outcomes' is a tautology that essentially restates the tool name. While it indicates a listing operation on appointment outcomes, it doesn't specify what 'list' means (e.g., retrieve all, paginated results, filtered by criteria) or differentiate from sibling tools like 'getAppointmentOutcome' (singular retrieval).

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. It doesn't mention sibling tools like 'getAppointmentOutcome' (for retrieving a specific outcome) or 'createAppointmentOutcome' (for creating new outcomes), nor does it specify any prerequisites, contexts, or exclusions for usage.

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