List Item Response Sets

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

Annotations already indicate read-only, idempotent, non-destructive, and open world. The description adds behavioral context: paginated JSON array, pagination metadata, and the Procore API endpoint. It does not contradict annotations and provides useful extra details.

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 four sentences, starting with the action, then usage, return type, pagination, and required parameter. It is relatively concise, though the Procore API line is somewhat extraneous but not harmful.

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 8 parameters and no output schema, the description covers pagination and required param but lacks specifics on response fields beyond 'paginated JSON array of Inspections' and pagination metadata. It is adequate but could be more complete about return structure.

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 baseline is 3. The description adds value by explaining how page and per_page control pagination and mentioning pagination metadata. It does not repeat all schema details, but the added context is meaningful.

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 lists 'Checklist Item Response Sets' for a specified company, using specific verbs and resource names. It distinguishes from siblings like create/delete/show by explicitly saying 'List' and mentioning paginated overview and filtering.

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 provides clear context on when to use the tool (enumerate inspections, get a paginated overview, find IDs, filter) and notes the required company_id. However, it does not explicitly state when not to use it or compare to alternatives like list_responses_in_the_specified_item_response_set.

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