list_today

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

With no annotations, the description carries full burden. It discloses core behavior: lists uncompleted, non-trashed tasks with start date today or before, ordered. However, it does not mention edge cases (e.g., tasks without start dates) or performance considerations. A 3 is appropriate.

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: two sentences plus a clarifying definition. Every sentence adds essential information—no fluff or redundancy. It is front-loaded with the main purpose.

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 presence of an output schema, the description adequately covers the filtering and ordering logic. However, the complete absence of parameter guidance makes it less than fully complete for effective invocation. A 3 reflects this balance.

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 two parameters (limit, offset) with 0% description coverage. The description adds no information about these parameters. An agent cannot infer valid values or effects from the description alone, making this a critical gap.

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 tool's function: listing tasks scheduled for today or earlier that are not completed. It defines 'today' precisely (start date today or before) and specifies ordering criteria (today_index then index). This differentiates it from sibling tools like list_upcoming or list_anytime.

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 implies usage for today's tasks but does not explicitly guide when to use this tool over alternatives like list_upcoming or list_inbox. No exclusions or context for when-not-to-use are provided.

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