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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the underlying endpoint (GET /tasks.json); it says nothing about pagination caps, default ordering, or result shape beyond the field list, which the schema largely supplies anyway.

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, front-loaded with the resource and returned fields, followed by the filtering capability and a usage example. No filler; the endpoint reference is the only marginal sentence.

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 16-parameter, zero-required list tool with no output schema, the description conveys the returned fields and the main filter dimensions, and the schema fills in pagination and formatting. It does not discuss paging strategy or default limits, a minor gap given the offset/page_token complexity.

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% with 16 well-documented parameters, including enums and format hints, so the baseline is 3. The description restates the filter axes (matter, assignee, status, priority, due-date range) but adds no syntax or constraint detail beyond what the 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 and resource ('List tasks') plus the fields it surfaces (status, priority, due date, matter, assignee), which is enough to distinguish it from clio_create_task and clio_update_task without opening either schema. The filterable dimensions are named explicitly.

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?

Gives clear usage context with a concrete scenario ('e.g. what is due this week') and names the filter axes that drive selection. It does not explicitly exclude or route to an alternative tool, but among the siblings the verb makes the division of labor obvious.

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