Habitica 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. 'Get' implies a read operation, but the description doesn't disclose any behavioral traits - no information about permissions needed, rate limits, what happens if the taskId doesn't exist, or the format/structure of returned checklist items. For a tool with zero annotation coverage, this is insufficient.

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 4 words, front-loaded with the core purpose. There's zero wasted language or redundancy. Every word earns its place in conveying the basic function.

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 no annotations, no output schema, and a read operation that likely returns structured data, the description is incomplete. It doesn't help the agent understand what will be returned (checklist item details, completion status, etc.) or any constraints on the retrieval. For a tool in a system with many related operations, more context is needed.

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% (taskId parameter is fully documented in schema), so the baseline is 3. The description adds no additional parameter information beyond what the schema already provides about the single required taskId parameter.

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 task checklist items' clearly states the action (get) and resource (task checklist items), but it's vague about scope - it doesn't specify if this retrieves all items for a task or has other limitations. It distinguishes from siblings like 'get_tasks' but not clearly from 'score_checklist_item' or 'update_checklist_item' which also involve checklist items.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions. With siblings like 'get_tasks' and various checklist manipulation tools, the agent receives no help in selecting this specific retrieval function.

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