things_list_items

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior beyond that: results are a bounded page and notes are omitted, which tells the agent what it will and won't receive. It could have mentioned ordering or the default page size, but the added context is substantive.

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?

Three compact sentences, front-loaded with the core purpose, then scope caveats, then filtering and the edit handoff. Every sentence carries information; nothing is padding.

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 does useful work by stating that summaries (not full notes) are returned and that IDs are usable for edits, and it flags pagination. It is nearly complete for a read-only list tool, missing only pagination mechanics and default sorting details.

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 0% across 8 params, so the description carries the explanatory burden and only partially meets it. It names four filtering dimensions (list, project_id, area_id, title query) but says nothing about kind, limit, offset, or status, leaving half the parameters to inference from enum values alone.

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 (read) and resource (a bounded page of task summaries, projects, or areas), and the plural 'page' framing distinguishes it from the singular things_get_task sibling. An agent can tell what it returns and at what granularity without opening the schema.

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 filtering guidance (by list, project_id, area_id, or title query) and a downstream workflow hint ('Use returned IDs for edits'), which tells the agent when this list tool is the right entry point. It stops short of explicitly naming when NOT to use it versus things_get_task, so it lands just below the top band.

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