planner_tasks

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds value by detailing derived fields (status from percentComplete, web_url from tid claim) and listing all returned fields. No contradictions with 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 a single paragraph with a clear front-loaded purpose. Although it lists many fields, it remains readable and not overly verbose. Could be slightly more structured, but it is concise enough.

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?

With output schema existing, the description's enumeration of return fields is somewhat redundant but adds clarity. However, it misses crucial context like pagination behavior (limit without continuation token) and how to obtain the required plan_id. This leaves the agent potentially uncertain about full usage.

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%, so the description must compensate. It explains bucket_id and status_filter with valid values and defaults, but does not describe plan_id (how to obtain) or limit (pagination behavior). This leaves gaps for half of the parameters.

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 'List tasks within a Planner plan,' which is a specific verb+resource combination. It distinguishes from sibling tools like 'planner_task_get' (single task) and 'tasks_assigned_to_me' (personal tasks) by focusing on plan-level tasks, but does not explicitly contrast them.

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 explains optional filtering by 'bucket_id' and 'status_filter', but does not provide guidance on when to use this tool versus alternatives like 'tasks_assigned_to_me' or 'planner_task_get'. No explicit when-not or context for choosing.

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