List Tasks in a Plan or Bucket

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds no new behavioral traits beyond what annotations and schema descriptions provide, such as default exclusions of completed tasks or pagination limits. It is accurate but minimal.

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?

Two concise sentences that front-load the core purpose and then mention optional filters. 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?

While annotations and schema cover most behavior, the description doesn't clarify the relationship between plan_id and bucket_id (whether both are needed, which takes precedence) or how this tool differs from planner_list_user_tasks. For a list-only tool with good schema coverage, this is adequate but leaves some usage 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?

Schema description coverage is 100%, so the baseline is 3. The description summarizes filters ('assignee user ID or open/completed state') which map to assigned_to and include_completed, but adds no extra detail beyond the schema's own parameter descriptions.

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's function: 'List Planner tasks in a plan (or a single bucket)' with a specific verb, resource, and scope. It distinguishes itself from siblings like planner_get_task (single task) and planner_list_plans (list plans) by focusing on tasks within a plan/bucket.

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 when to use the tool (when you need tasks in a plan/bucket) but does not explicitly state alternatives or exclusions. It could differentiate from planner_list_user_tasks, but no such guidance is provided.

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