Show Checklist Item Response

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

Beyond the readOnlyHint annotation, the description explicitly states 'Read-only — it changes nothing in Procore,' documents failure modes (401/403/404), and notes the project_id default behavior from procore_set_config, adding meaningful operational context.

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?

Dense but well-structured: purpose, usage, parameter defaults, return type, safety, error semantics, required params, and API reference. Every sentence adds value and is logically organized with clear sentences.

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 simple read tool with no output schema, the description covers purpose, preconditions, defaults, return shape (single JSON object), safety, and error codes. No essential aspect is missing, and it is self-sufficient for an agent to select and invoke it 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?

Schema descriptions are basic (URL path parameter identifiers). The description significantly enriches them by explaining project_id defaults to the config value when omitted and that item_id must identify an existing parent record, resolvable via a list tool. This goes well beyond the schema.

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 opens with a specific verb and resource: 'Returns the Checklist Item Response for a specified Checklist Item.' This clearly distinguishes it from sibling list/create/delete tools, especially with the usage phrase 'when you already know which checklist item response you want.'

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?

Explicitly states when to use this tool ('Use this when you already know which checklist item response you want and need its full field set') and instructs resolving the item_id with 'the matching list tool first,' providing clear guidance versus listing tools.

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