list_planner_plans

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

With no annotations, the description carries the full behavioral burden)Skip. It discloses caching behavior, the refresh flag's effect, and the account-scoped visibility. It doesn't mention auth requirements or potential side effects, but for a list operation with one parameter, the disclosed caching semantics add meaningful transparency beyond the schema.

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 with no filler. The primary purpose is front-loaded, and the caching/refresh detail is placed second, making the most important information immediately accessible.

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 a simple operation, one parameter, and an existing output schema, the description covers purpose, scope, and the refresh parameter. It doesn't mention login requirements or error conditions, but those are likely implied by the sibling auth tools and don't impede correct 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?

The schema provides only a boolean with a default, but the description fully explains the parameter's semantics: 'pass refresh=true to force a re-read' with a concrete example. This is exactly the kind of meaning the schema alone cannot convey.

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 uses a specific verb ('List') and resource ('Planner plans'), explicitly scopes to plans 'this account can see', and notes that it returns buckets and IDs. This clearly differentiates it from sibling tools like list_planner_tasks and create_planner_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 gives a concrete usage trigger for the refresh parameter ('after someone added a bucket in the Planner UI') but does not explicitly state when to choose this tool over alternatives such as list_planner_tasks. The implied context is clear, but no exclusions or alternative routing are provided.

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