List Company Checklist Sections

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

The description provides pagination behavior, response format (JSON array and remaining pages), common error statuses (401/403/404), and explicitly states it is read-only. These details go beyond the annotations, which only declare readOnly and idempotent hints.

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 reasonably sized, covering purpose, usage, errors, and endpoint in about 100 words. It is front-loaded with the primary purpose and contains no fluff. The API category and endpoint duplication could be seen as slightly redundant but still useful.

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 no output schema, the description adequately explains the JSON array return and pagination. It lists required parameters, describes default behavior, and covers common error statuses. Combined with the schema and annotations, an agent has sufficient context to invoke the tool correctly.

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?

The schema already documents all four parameters with 100% coverage. The description adds context that company_id can be omitted to fall back to the configured value and that page/per_page control pagination with remaining-pages reporting, which is useful but not essential.

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 a list of Checklist Sections for a given Company List Template, with a specific endpoint. However, it does not differentiate from the similarly named sibling 'list_company_checklist_template_sections', which could cause confusion.

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 explicitly says to use this tool to discover company checklist sections or to look up an id before calling another tool. It also notes the default for company_id via procore_set_config. It does not name alternatives or exclusions, but the read-only nature is clear.

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