List Checklist List Specification Section Filter Options

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

Annotations indicate readOnlyHint, destructiveHint false, idempotentHint true. Description adds that it returns a JSON array and supports pagination, which is consistent with read-only behavior. Does not contradict annotations, and adds useful context about output format and pagination.

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?

Description is concise at 4 sentences, front-loading purpose, then usage, then output, then required parameter. No wasted words and well-organized.

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 is a simple filter options list, the description covers purpose, usage, output format, required parameter, pagination, and even cites the Procore API endpoint. No output schema exists, but the return type is mentioned. Nearly complete for this type of tool.

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 has 100% description coverage for all 3 parameters (project_id, page, per_page), so the schema already explains each. The description repeats that project_id is required and mentions pagination, but adds minimal extra meaning. Baseline 3 is appropriate as schema does the heavy lifting.

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?

Description clearly states the verb 'List', the resource 'Checklist List Specification Section Filter Options', and explains the purpose: to enumerate Inspections for a paginated overview, finding IDs, or filtering by query parameters. It distinguishes itself from sibling filter option tools by specifically targeting specification sections.

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?

Provides explicit usage guidance: 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' This gives context but does not explicitly state when not to use or mention alternatives, leaving some ambiguity.

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