List Checklist List Closed By Contact Filter Options

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

With annotations indicating read-only and idempotent behavior, the description adds value by mentioning pagination and search capacity. This goes beyond the structured annotations, though it omits details like error handling or rate limits.

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 very concise with four sentences. It starts with the core function, adds usage advice, specifies the return type, and ends with required parameters and API details. No wasted text.

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?

Given the tool's role as a filter options list, the description covers the return type, pagination, search, and required parameters. It provides the endpoint but lacks details on output shape (no output schema exists). This is sufficient for a read-only filter list.

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 coverage is 100%, so each parameter has a description. The description only reiterates required parameters and implies the use of page/per_page and query for pagination/search, adding minimal semantic value beyond the schema.

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 clearly states it returns contacts with closed inspections and provides pagination/optional search. It specifies the return type (JSON array of filter values). However, it does not differentiate from sibling filter option tools like the v1 version.

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 description advises using it to enumerate inspections for a paginated overview, finding IDs, or filtering with query parameters. It mentions required parameters but lacks guidance on when not to use it or alternatives, such as other filter option tools.

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