Show Response

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

Annotations declare readOnlyHint and idempotentHint, and the description reinforces 'Read-only — it changes nothing in Procore.' It adds valuable error semantics (401/403/404) and notes company_id defaulting to procore_set_config, going beyond the structured annotations.

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 dense but organized: purpose, usage, defaults, return format, read-only note, error payloads, required params, and API endpoint are all covered. No filler, though the read-only statement slightly overlaps with annotations.

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?

With just two required params and no output schema, the description covers return type (single JSON object), preconditions (resolve id first), error behaviors, and endpoint mapping. It doesn't enumerate response fields, but the 'full field set' phrase and the simple resource type make this adequate.

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?

Both parameters are documented in the schema (100% coverage), so baseline is 3. The description adds meaning by clarifying company_id default behavior and that id must refer to an existing parent record resolvable via the list tool, going beyond simple path parameter labels.

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 opens with 'Returns a specified Response' and explicitly states when to use ('when you already know which response you want and need its full field set'), clearly distinguishing it from list/create/update siblings like list_responses and create_a_response.

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 context: 'Use this when you already know which response you want...' and instructs to resolve id with the matching list tool first. This contrasts effectively with listing alternatives and sets a precondition.

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