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. It states 'Get a pond by ID' but doesn't disclose behavioral traits such as whether it's a read-only operation, what happens if the ID is invalid (e.g., returns null or error), rate limits, or authentication needs. This leaves significant gaps in understanding the tool's behavior.

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 with 'Get a pond by ID', a single sentence that front-loads the purpose without any wasted words. It efficiently communicates the core action and key input, making it easy to parse quickly.

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 simplicity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't explain what is returned (e.g., pond details, error responses) or behavioral aspects like idempotency or side effects, leaving the agent with insufficient context for reliable use.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'Pond ID'. The description adds no additional meaning beyond this, as it only repeats 'by ID'. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter semantics.

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 'Get a pond by ID' clearly states the action (get) and resource (pond), but it's vague about what 'get' entails—does it retrieve details, metadata, or something else? It distinguishes from siblings like 'listPonds' and 'createPond' by specifying retrieval by ID, but lacks specificity on the scope of data returned.

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. For example, it doesn't clarify if this should be used for fetching a single pond's details after listing ponds or if there are prerequisites like authentication. The description implies usage by ID but offers no context on error handling or alternatives.

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