tasks_of_today

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

With no annotations, description bears full burden. It states it returns active tasks for a day but fails to disclose defaults (e.g., local_date null meaning today), inclusion of subtasks, handling of tasks without due dates, or read-only status. Significant gaps for a query 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?

Extremely concise: three lines for core description plus meta tags. No redundant phrasing. Front-loaded with the primary purpose. Efficiently structured.

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 8 params, no output schema, and 0% schema coverage, the description omits crucial details like return format, default behavior of local_date, and meaning of 'active' tasks. Leaves many operational questions unanswered.

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%, yet description only adds that 'Multi-value filters accept either a list or a single string.' No explanation of local_date, text_query, limit, or what 'active tasks' implies. Very little value added beyond schema types.

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?

Description clearly states it returns 'active tasks scheduled for a given local day', specifying verb and resource with a clear constraint (local day). This distinguishes it from siblings like events_of_today (events) and overdue_tasks (overdue tasks).

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?

Lists related tools (query_agenda, events_of_today, overdue_tasks) providing context for when to use alternatives. Includes usage note about multi-value filters accepting list or string. However, lacks explicit 'when not to use' guidance.

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