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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real value by defining the status lifecycle semantics — notably that completed is self-reported, confirmed is a second-party sign-off, and verified comes from a later Diagnostic observing the fix externally. It also explains that an empty page means nothing matched these filters, which prevents the agent from misreading an empty result as an error.

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?

The description is front-loaded with scope and ordering, then moves to return fields, statuses, filters, and empty-page behavior with almost no filler. The long enumeration of returned fields is dense but justified because no output schema exists.

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 carries the return-value burden and does so by enumerating the item fields, and pagination is handled by the schema's limit and cursor parameters. It is nearly complete, though it omits whether additional pages exist in the response envelope or how to detect the end of a result set beyond the cursor.

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 only 40%, with status, client_id, and source_id undocumented in the schema, but the description compensates by naming all three as filters and mapping source_id to the originating Diagnostic in the returned-field list. It does not spell out combination semantics or uuid format expectations beyond what the schema's format field already conveys.

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 first sentence states a specific verb and resource ('Lists the action items'), scopes it to the connected account, and specifies ordering ('newest first'). It is clearly distinguishable from the singular sibling get_action_item, which returns one item rather than a page.

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?

The closing sentence gives concrete usage contexts ('what should we fix first' and progress reviews), so the agent knows the intended scenarios. It stops short of explicit when-not guidance or naming alternatives such as get_action_item for single-item retrieval, which keeps it below a 5.

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