List Available Checklist Item Types

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

Annotations indicate a safe read operation (readOnlyHint=true), but the description contradicts itself by mixing checklist item types with inspections, misleading about the returned data. It mentions pagination but does not clarify the exact behavior or response structure beyond what schema already provides.

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 includes unnecessary details like 'Procore API: Project Management > Inspections' and the full endpoint URL, which may be irrelevant for an AI agent. It is also repetitive and misaligned with the tool name, reducing conciseness.

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?

The description is incomplete and misleading. It fails to clarify that the tool lists checklist item types, not inspections, and does not explain what an item type is or how the response aligns with the tool name. No output schema exists to compensate.

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%, providing standard baseline. The description adds the crucial note that only one of project_id or company_id is needed despite both being marked required, and explains pagination usage. However, it also repeats 'Required parameters: project_id, company_id' which contradicts this note.

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 states 'Lists available Checklist Item Types' but then says 'enumerate Inspections' and 'Returns a paginated JSON array of Inspections', creating a mismatch between the tool name and described behavior. This confusion undermines purpose clarity.

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 explains that only one of the two required parameters needs to be passed, which is a helpful usage note. However, it does not differentiate this tool from siblings like 'list_checklist_templates' or specify when to choose this over alternatives.

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