list_today

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

With no annotations, the description carries the full burden, and it does disclose the non-obvious inclusion semantics — overdue-but-undone items are pulled in alongside same-day and due-by-then items. It says nothing about permissions or ordering, but the return shape is covered by the output schema.

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 compact lines with zero filler; scope rules come first, then the parameter format. Nothing redundant is included.

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 single-parameter read tool with an output schema, the essentials are covered: what is included in the result set and how to format the day argument. The only gap is the unnamed resource and no cross-reference to list_due.

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 description coverage is 0%, so the description must compensate, and it does: it documents the accepted formats (YYYY-MM-DD plus the today/tomorrow/yesterday keywords), with the default visible in the schema. It adds meaning well beyond the bare 'string' type.

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 telegraphic phrasing "What's on for a day" implies listing items for a given day, and the three inclusion rules (do-date that day, overdue do-dates, due-by-then) define scope quite precisely. However, it never states the resource cleanly (tasks vs. anything else) and does not distinguish itself from the overlapping sibling list_due.

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?

There is no when-to-use guidance and no mention of list_due, the sibling with the most obvious overlap (due items). The agent must infer that this is the day-scoped view and list_due the unfiltered one.

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