Create Checklist Item Response

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

Annotations already flag non-idempotent and non-read-only behavior, but the description adds valuable context: non-idempotency ('calling it again creates another record'), error payload semantics (401/403/404), project_id defaulting, and automatic nesting of fields under item_response. This exceeds the annotation baseline.

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 longer than minimal, but every sentence adds necessary detail—formats, prerequisite resolution, defaults, error codes, and endpoint. It is front-loaded with the purpose and organized logically, so the length is justified, though not as tight as a two-sentence ideal.

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?

For a 7-parameter create tool with no output schema, the description covers essentials: required params, optional payload formats, item-type constraints, defaulting behavior, error codes, and non-idempotency. It also provides the API endpoint and section for further reference, making it sufficient for an agent to invoke 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?

With 100% schema description coverage, the baseline is 3, but the description adds meaningful parameter semantics: it clarifies that exactly one payload format should be used per item type, that fields are top-level arguments nested internally, and that project_id can be omitted to use the config default. This elevates the score.

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 the tool creates a checklist item response for a specified checklist item, and explicitly notes that calling it again creates a new record, distinguishing it from show/delete/list siblings. It also enumerates the payload formats, making the tool's purpose concrete and actionable.

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 usage context: it instructs to resolve item_id with a matching list tool first, explains that project_id defaults from procore_set_config, and clarifies that payload fields are passed as top-level arguments. It does not explicitly name alternatives or when-not-to-use, but as a create tool, this is strong guidance.

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