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. 'List all smart lists' implies a read-only operation, but it doesn't disclose important behavioral traits like whether this requires authentication, rate limits, pagination behavior (beyond what's in the schema), error conditions, or what format the results will be in. The description is minimal and lacks behavioral context.

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 at just three words, with zero wasted language. It's front-loaded with the core purpose and contains no unnecessary elaboration. This is an example of efficient communication where every word earns its place.

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 read operation with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what a 'smart list' is in this context, what fields are returned, whether results are paginated (beyond the schema parameters), or what authentication is required. For a tool with 3 parameters and no structured output documentation, the description should provide more contextual information.

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 schema description coverage is 100%, with all three parameters (limit, offset, next) clearly documented in the schema. The description adds no parameter information beyond what the schema provides, which is acceptable given the high schema coverage. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 all smart lists' clearly states the verb ('List') and resource ('smart lists'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'getSmartList' (singular retrieval) or other list tools, but the specificity of 'smart lists' as the resource provides adequate clarity.

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 when to use 'listSmartLists' versus 'getSmartList' (singular retrieval) or other list operations, nor does it provide any context about prerequisites, typical use cases, or limitations.

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