get_tasks_between

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

With no annotations provided, the description must carry behavioral context. It discloses that the range is inclusive, that it retrieves all tasks, and that tag filtering is optional. It does not describe ordering, pagination, or timezone handling, but the read-only nature is clear from 'Retrieve.'

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. The core behavior appears in the first sentence, the usage guidance in the second, and the optional parameter in the third. Every sentence adds unique value with no repetition.

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 query tool with an output schema, the description covers purpose, usage context, date format, inclusive boundaries, and optional filtering. An agent can both select this tool over get_tasks_by_date and construct a correct call without further information.

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. It adds the date format YYYY-MM-DD, explains the inclusive range semantics, and clarifies that tag is an optional filter. It does not explicitly document start_date and end_date individually, but the meaning is sufficiently inferable.

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 begins with a specific verb and resource: 'Retrieve all logged tasks within an inclusive date range.' It also clearly distinguishes itself from the sibling get_tasks_by_date by framing this tool as the range-based alternative.

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?

It explicitly states when to use the tool ('what did I do last week' style questions) and names the alternative approach it replaces ('instead of calling get_tasks_by_date multiple times'). This gives an agent a clear decision rule.

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