find-tasks-by-date

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is clear. Description adds value by explaining that startDate='today' includes overdue items and default filtering excludes others' tasks, but lacks broader behavioral context (e.g., pagination, performance).

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?

Three concise sentences, no fluff. First sentence nails purpose, subsequent ones add important details. Could be slightly more structured (e.g., bullet points) but is efficient.

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 9 parameters with full schema descriptions and output schema present, description covers key behavioral nuances but lacks guidance on combining parameters or common use cases. Adequate for a retrieval tool but not exhaustive.

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 coverage is 100%, so baseline is 3. Description mentions only two parameters' behaviors (startDate, responsibleUserFiltering), adding marginal value beyond schema. Could provide more examples or clarification for other params.

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?

Clearly states 'Get tasks by date range' with specific verb and resource. Distinguishes from find-tasks by focusing on date-based queries, but could explicitly differentiate from sibling tool find-tasks.

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?

Provides some guidance: defaults for startDate and responsibleUserFiltering, and requirement for responsibleUser in personal queries. However, no explicit when-to-use/when-not-to-use or alternative tool names.

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