todo_list_items

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

The description discloses that status filtering happens client-side, which is a behavioral trait beyond the schema. However, with no annotations, other behavioral aspects like pagination, limits, or return structure are not mentioned, leaving gaps for a listing 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 very concise with two sentences. The first sentence front-loads the purpose, and the second provides parameter details. No redundant information.

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 low complexity (2 parameters), presence of output schema, and the description covering the main intent and a key parameter behavior, it is mostly complete. The missing explanation for 'entity_id' is minor as it is implied.

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 0%, so the description must compensate. It explains the 'status' parameter with typical values, but does not explain 'entity_id' as the todo list identifier. This adds some value but is incomplete.

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 tool lists items in a todo list via a specific WebSocket endpoint, which is a specific verb+resource. It distinguishes itself from sibling tools like todo_add_item or todo_list_todo_lists by implying it deals with items within a list, not the lists themselves.

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 listing items but does not provide explicit guidance on when to use this tool versus alternatives like adding, removing, or updating items. It lacks when-not-to-use instructions or alternative suggestions.

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