List today's tasks

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

readOnlyHint and openWorldHint annotations already establish the safe, non-exhaustive nature. The description adds the scoping logic, but it leaves ambiguity about whether 'due today' includes completed tasks and does not disclose default return verbosity. This aligns with the baseline for annotation-covered tools.

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 a single sentence, front-loaded with the verb, and contains no filler. The parenthetical adds precise filter criteria and the optional board filter is conveyed efficiently.

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 read-only list tool with full schema and annotation coverage, the description covers the essential relevance criteria. It does not explain the return format, but the 'detailed' parameter and openWorldHint provide some indication; a dedicated output schema would improve completeness.

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?

All 6 parameters have schema descriptions (100% coverage), so the description adds little beyond what the schema already provides. The only addition is confirming the board filter is optional, which is also apparent from having zero required parameters.

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 verb 'List' and the resource 'tasks relevant for today', with explicit inclusion criteria (assigned to me and not done, or due today). This distinguishes it from siblings like list_tasks and list_calendar_tasks by specifying the daily relevance filter.

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 clear context: it is for today's relevant tasks, with an optional board filter. It does not explicitly mention alternatives or exclusions, but the daily relevance criterion and optional board filter imply the appropriate scenario.

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