get_forecast_tasks

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

Annotations declare readOnlyHint=true and idempotentHint=true, so the description adds value by mentioning 'direct subtask counts and optional subtask-tree expansion' but omits details on output format, pagination, or time window (covered in schema). It neither contradicts nor significantly enhances the 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 sentence of 12 words, front-loading the core purpose and key features. Every word is necessary; there is no redundancy or fluff.

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 the absence of an output schema, the description could elaborate on the result format (e.g., task list with subtask counts) or the definition of 'forecast' (e.g., tasks due within days). The schema covers parameters, but the description lacks enough context for an agent to fully understand the output or behavior.

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?

With 100% schema description coverage, the input schema already describes all five parameters. The description's phrase 'subtask-tree expansion' relates to showSubtasks and maxSubtaskDepth but adds no new semantic value beyond what the schema provides.

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 explicitly states 'Get forecast tasks', identifying the verb (get) and resource (forecast tasks), and adds detail about subtask counts and expansion, distinguishing it from sibling tools like 'get_inbox_tasks' or 'get_flagged_tasks' that focus on specific categories.

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 usage for retrieving forecast tasks but does not provide explicit guidance on when to use this tool versus alternatives like 'filter_tasks' or 'get_tasks_by_tag'. No when-not-to-use or context exclusions are mentioned.

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