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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds the response shape and the underlying GET endpoint, but says nothing about pagination behavior or rate limits that the cursor parameter implies.

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?

A single front-loaded sentence plus the endpoint path, with no filler. It loses a point because 'state (empty/yes/no/not_applicable)' describes an output field but uses the same word as the input `state` parameter whose enum is active/deleted, which can momentarily blur which 'state' is meant.

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 no output schema, the description compensates by naming the returned fields, and the schema covers the pagination cursor and filter parameters. It is complete enough to call correctly, though pagination flow is left entirely to the schema.

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 all four parameters (project_id, state, per_page, last_synced_at) are already documented in the schema. The description adds no parameter-level detail, which is the correct baseline when the schema does the heavy lifting.

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 a specific verb+resource (list checklist items across all tasks in a project) and enumerates the returned fields (name, checked flag, state, task_id), so an agent knows exactly what comes back. It does not explicitly contrast itself with siblings like fieldwire_list_tasks, but the resource is unambiguous.

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?

Usage is only implied: it scopes to 'all tasks in a project' and hints the task_id links items back to tasks, but there is no explicit when-to-use statement, no mention of prerequisites, and no routing away from alternatives such as fieldwire_list_tasks or fieldwire_get_task.

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