add_to_plan

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

No annotations are provided, so the description bears full responsibility. It mentions adding a task but does not disclose any side effects, required permissions, or constraints (e.g., can the same task be added multiple times to the same day?). This is insufficient for full transparency.

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 extremely concise with two sentences, front-loaded with the primary action. No wasted words.

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 has an output schema (not shown), so return value details are not required. The description adequately covers the main behavior and parameter semantics. Minor gaps: no mention of whether the plan must exist or if the task can be added without a plan.

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 input schema has 0% description coverage, so the description adds crucial meaning: it clarifies that task_id is a UUID of an existing task and that date defaults to today. This goes beyond the raw 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?

The description clearly states the action ('Add a task') and the target resource ('the daily plan'). It differentiates from siblings like 'add_to_items_plan' by specifying 'daily plan' and from 'remove_from_plan' by being an add operation.

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 parameter semantics (task_id is UUID, date defaults to today) but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare with alternatives like 'add_to_items_plan' or 'batch_tasks'.

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