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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is clear. The description adds filter dimensions and offset pagination support, but does not disclose auth needs, rate limits, return shape, or pagination mechanics such as cursor vs offset.

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 with no filler; the operation scope is front-loaded and the pagination note follows. Every sentence carries useful information for a listing tool.

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 10-parameter tool with a nested query object, only 20% schema description coverage, and no output schema, the description is too sparse. It does not explain most filter parameters, pagination mechanics, or the returned task shape.

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 20%; the description names only status, assignee, and ownership (likely the mine boolean) while omitting limit, cursor, offset, query, brand_id, workspace_id, include_completed, defaults, and format constraints. It adds minimal meaning beyond what the sparse schema already provides.

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 (list) and resource (workspace tasks), plus scope (filtering by status, assignee, ownership) and pagination. It does not explicitly distinguish from sibling tools like get_task or list_posts, but the operation and resource are 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?

Implies use for listing tasks with optional filters and pagination, giving minimal usage context. It does not say when to use this vs get_task, search, or other list endpoints, nor does it state exclusions or prerequisites.

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