planner_list_buckets

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

No annotations are provided, so the description carries the full behavioral burden; the word 'List' at least signals a read-only, non-destructive operation. However, it discloses nothing about permissions, ordering, pagination, or behavior for an invalid plan_id, which is a real gap for an unannotated 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?

One short sentence with no filler and the resource front-loaded after the verb. It is efficient, though the brevity borders on under-specification rather than tight writing.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be explained. Still, the description omits where plan_id comes from and offers no differentiation from the many sibling planner/todo list tools, leaving a small but real gap.

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% and the single required parameter plan_id is not mentioned at all. The phrase 'of a plan' only loosely implies that plan_id identifies the target plan, adding almost no syntax or format detail beyond the bare 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?

States a specific verb ('List') and resource ('buckets (columns) of a plan'), and the parenthetical clarifies the Planner-specific term 'bucket' for agents unfamiliar with it. It does not distinguish itself from siblings like planner_list_plans or planner_list_tasks, so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. Usage is only inferable from the verb-plus-resource phrasing, and nothing tells the agent to call planner_list_plans first to obtain a plan_id.

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