RTM 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. It states 'Rename a task' and mentions returns 'Updated task details', which implies a mutation operation, but lacks critical details such as permission requirements, whether the rename is reversible, error handling for invalid inputs, or how it interacts with other task properties. 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 structured with a clear purpose statement followed by Args and Returns sections, making it easy to parse. It avoids unnecessary fluff, but the parameter explanations are minimal and could be more informative without sacrificing brevity, slightly reducing efficiency.

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 complexity (5 parameters, mutation operation) and no annotations, the description is moderately complete: it covers the basic purpose, parameters, and return indication. However, with an output schema present, it doesn't need to detail return values, but it lacks behavioral context and usage guidelines, making it adequate but with clear gaps for effective agent 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 description lists all 5 parameters with brief labels (e.g., 'new_name: New name for the task'), adding basic semantics beyond the schema's 0% coverage. However, it doesn't explain parameter relationships (e.g., that 'task_id' or 'task_name' with 'list_id' might be needed to identify the task), default behaviors, or constraints, which limits its helpfulness despite compensating somewhat for the low schema coverage.

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 clearly states the verb ('Rename') and resource ('a task'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'rename_list' or explain how this differs from other task modification tools such as 'set_task_due_date' or 'set_task_priority', which prevents a perfect score.

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 prerequisites (e.g., needing task identification), exclusions, or comparisons to sibling tools like 'rename_list' for lists or other task-setting tools, leaving the agent with minimal context for selection.

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