find-tasks-by-date

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful behavior beyond this: startDate='today' includes overdue items, the default responsibleUserFiltering excludes others' tasks, and person-specific queries need responsibleUser. No contradiction with the annotations was found.

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 compact and front-loaded: a clear purpose sentence followed by three high-value behavior notes. Every sentence earns its place, and there is no redundant or distracting text.

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?

Annotations cover safety semantics, the output schema covers return shape, and the input schema fully documents all parameters. The description adds the most important interpretive context such as overdue and responsible-user defaults, making this sufficiently complete for a read-only list tool.

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 100%, so the baseline is provided by the input schema itself. The description adds value by highlighting the key default filtering behavior and the responsibleUser requirement, but most of this information already appears in the schema.

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 opens with 'Get tasks by date range', which is a specific verb+resource statement and clearly scopes the tool to date-based retrieval. However, it does not explicitly differentiate from sibling tools such as find-tasks or find-completed-tasks, so it stops short of full distinction.

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 no tool-selection guidance on when to use find-tasks-by-date versus siblings like find-tasks or find-completed-tasks. It does explain that person-specific queries require responsibleUser, but that is parameter configuration guidance rather than usage-vs-alternative guidance.

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