todowrite

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It mentions session scoping but does not disclose whether the tool replaces the entire list or merges, whether it is destructive, or what the return value is. For a write tool, these are significant gaps.

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 short and front-loaded with the action. The first sentence is essential, but the second sentence merely restates what the schema already says, making it somewhat redundant. Overall, it is concise 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 simple tool with a single parameter and no output schema, the description provides the core purpose and item structure. However, it lacks clarity on how the list is maintained (whether the whole list is replaced or merged), which is important for correct usage. It is minimally complete but has gaps.

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 fully documents the 'todos' parameter with descriptions for content, status, and priority (100% coverage). The description only repeats that items have content, status, and priority, adding no additional semantics or examples beyond the schema.

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 a specific verb ('Create and maintain') and a specific resource ('structured task list for the current MCP session'). It distinguishes the tool from all siblings, which are unrelated (file ops, shell, web). This fully clarifies what the tool does.

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 implies usage for managing a session-scoped todo list, but does not explicitly state when to use it versus alternatives or when not to use it. Since sibling tools are unrelated, there is low ambiguity, but explicit guidance is absent.

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