Agentic Tools 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. It discloses key behavioral traits like 'Supports unlimited nesting depth' and implies mutation (moving tasks), but lacks details on permissions, error conditions, or what happens to subtasks during the move. It adds some value but leaves gaps for a mutation tool.

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 front-loaded with the core purpose in the first sentence, followed by specific usage guidance and a behavioral note. Every sentence earns its place with no wasted words, making it highly efficient and easy to parse.

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?

For a mutation tool with no annotations and no output schema, the description is adequate but incomplete. It covers the basic operation and nesting behavior, but lacks information on return values, error handling, or side effects (e.g., impact on subtasks), which are important for contextual understanding.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value by clarifying 'newParentId' usage (optional for top level), but does not provide additional meaning beyond what's in the schema descriptions for 'taskId' or 'workingDirectory'.

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 ('move') and resource ('task'), specifies the action ('to a different parent in the hierarchy'), and distinguishes from siblings like 'update_task' or 'create_subtask' by focusing on repositioning rather than content modification or creation.

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 clear context for usage ('Set newParentId to move under another task, or leave empty to move to top level'), but does not explicitly mention when NOT to use it or name specific alternatives among siblings like 'update_task' for other modifications.

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