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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new context beyond that: the returned field set, the cross-tool id-resolution dependency, and the underlying GET endpoint, though it omits pagination behavior despite the last_synced_at cursor.

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?

It is compact and front-loads the resource, then fields, then filters, then id resolution. The fragments are dense and slightly list-like rather than prose, and the trailing raw endpoint is the weakest element, but nothing is wasted.

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?

With 18 parameters, no output schema and a cursor parameter, the description usefully compensates by enumerating the returned fields and the filter surface. The main missing piece is pagination semantics around last_synced_at, which the schema hints at but the description never explains.

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 3. The description earns an extra point by mapping the UUID filter params to the sibling tools that produce them (statuses, teams, locations, project users), which the schema itself does not tell an agent.

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 names the resource (tasks, with synonyms punch items/issues) and its project scope, then enumerates the fields returned and the filters available, which makes the tool's job unambiguous against the single-task sibling fieldwire_get_task. It never uses an explicit verb, relying on the name, so it falls just short of the crispest tier.

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 gives concrete usage context: which filters exist and, importantly, which sibling tools to call to resolve status/team/location/user ids before invoking this one. It stops short of explicit when-not guidance (e.g., use fieldwire_get_task for a single item, or the pagination contract), so no 5.

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