List a User's Tasks

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

Annotations already declare the tool safe and read-only. The description adds useful behavioral context about the cross-plan scope and the dependency on planner_find_user to obtain the user ID, without contradicting the annotations.

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 two sentences, front-loads the core purpose, and adds a practical prerequisite. No wasted words.

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 list tool with strong annotations and fully documented parameters, the description is sufficient. It clarifies the exact scope and prerequisite, which covers essential context. It omits no critical behavior needed for invocation.

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 coverage is 100%, with each parameter already described. The description adds minimal semantic value beyond the schema, only reinforcing that user_id is central to the 'assigned to a user' scope. Baseline 3 is appropriate.

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 states the verb 'List' and specifies the resource: 'all Planner tasks assigned to a user across every plan they participate in'. This clearly distinguishes it from sibling tools like planner_list_tasks by emphasizing the user-centric, cross-plan scope.

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 and a workflow hint ('Get the user ID from planner_find_user'), but it does not explicitly mention alternatives or when not to use this tool. This falls short of a 5 because no exclusions are stated.

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