summarize_today

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description adds that output is aggregated per list and includes overdue tasks. No contradictions. Brief but sufficient for a read-only summary 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?

Two sentences, front-loaded with purpose and usage. No extraneous words. Highly efficient.

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?

For a simple tool with two optional parameters, no output schema, and read-only semantics, the description adequately covers purpose and usage. The output format dependency on verbose is noted. More detail on the aggregated structure would be helpful but not necessary.

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 50% (verbose has description, time_zone lacks). Description does not add meaning for time_zone beyond schema's lack of description. For verbose, it clarifies the impact on output format. Does not fully compensate for missing time_zone parameter description.

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 summarizes tasks due today and overdue, aggregated per list, directly answering the question 'what do I have to do today?'. This distinguishes it from sibling tools like list_all_tasks or list_overdue_tasks which provide raw lists.

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?

Explicitly states it is useful for the daily summary question, providing clear usage context. Does not explicitly mention when not to use or alternatives, but the purpose is specific enough.

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