get_daily_plan

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

With no annotations, the description carries full burden. It discloses how the plan auto-seeds from recurring tasks, carries forward incomplete items, and includes due items. It also explains timezone handling and parameter defaults. No side effects or destructive actions are indicated, which is appropriate for a read-only 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?

The description is well-structured with a clear intro followed by parameter details. It is concise without unnecessary text, though the parameter documentation could be slightly more compact. Every sentence contributes to understanding.

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 tool has only 2 optional parameters, no required fields, and an output schema (not shown), the description covers all essential aspects: behavior, parameter semantics, and timezone handling. It is complete and leaves no critical gaps.

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 coverage is 0%, so the description must compensate. It explains both parameters in detail: date format (YYYY-MM-DD), default behavior (today in user's timezone), and timezone (IANA format, persistence after first use). This adds significant value 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 'Return today's curated daily plan' and explains its contents (recurring tasks, incomplete items, due items). It is specific about the verb and resource, but does not explicitly differentiate it from sibling tools like get_items_plan or get_calendar_events.

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 provides guidance on when to supply the timezone parameter and mentions that the date defaults to today in user's timezone. However, it does not discuss when to use this tool versus alternatives or note any prerequisites.

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