tasks_list_planner_buckets

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

Annotations already mark this as read-only and idempotent. The description adds the permission requirement ('Requires Tasks.Read') and clarifies what buckets represent ('typically stages such as To Do, In Progress and Done'). It also indicates the output includes id and name, providing useful beyond-annotation information.

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?

Three sentences, each contributes meaningfully: the first states the action and output, the second explains the concept of buckets, and the third covers usage and permission. There is no redundancy or filler.

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 list tool with strong annotations and 100% schema coverage, the description covers purpose, prerequisite, use cases, output fields (id, name), and permission, making it self-contained and sufficient for an agent to invoke correctly.

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 sole parameter plan_id is well-described in the schema, and the description adds provenance by noting the ID comes from tasks_list_planner_plans, which aids correct invocation. This goes beyond the schema's 'The Planner plan ID to list buckets for'.

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 opening phrase 'List the buckets (columns) in a Planner plan, with id and name' clearly identifies the verb (list) and resource (buckets in a plan). It differentiates from sibling tools like tasks_list_planner_plans and tasks_list_planner_tasks by focusing on a specific aspect of planner data.

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?

It states to take a plan id from tasks_list_planner_plans, giving a clear prerequisite, and provides explicit use cases: 'when a task needs placing in the right column, or to report on how work is distributed across a board.' This gives strong contextual guidance, though it doesn't explicitly name alternative tools to avoid.

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