batch_filter_tasks

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses batching semantics (one call replaces N calls), but says nothing about the result shape, whether tasks are grouped by project, or how the per-project limit interacts with aggregation – all material for a 27-parameter tool with no output schema.

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?

Two sentences, zero waste, and the PREFERRED/preferred-selection cue is front-loaded ahead of the condition. Nothing here needs to be trimmed or reordered.

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 27-parameter, zero-required, no-output-schema read tool, the description nails routing but stops short of telling the agent what comes back – whether results are keyed by project, whether a missing project ID errors or is skipped, and how limit applies per project. Those gaps are only partly covered by the schema's per-field notes.

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 every parameter including limit, sortBy and the date-window flags is already documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies rather than anything higher.

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?

States a specific verb and resource ("Filter tasks") with a clear scope ("across multiple projects in ONE call"). It explicitly names the sibling it is not (filter_tasks) and the condition that separates them, so an agent can tell them apart without opening either schema.

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?

"Always use this instead of multiple filter_tasks calls when querying 2+ projects" names the alternative and the triggering condition in one sentence. The only mild gap is that the single-project or single-task query case is left implicit, but the decision rule itself is unambiguous.

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