Show Company Checklist Template

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

Beyond annotations, the description adds valuable behavior: company_id defaults to procore_set_config, returns a single JSON object, is explicitly read-only, and details common failure modes (401 expired token, 403 missing permission, 404 bad id). This exceeds what annotations alone provide.

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 substantive yet efficient. Every sentence serves a purpose: purpose, use-case, parameter behavior, return type, safety, errors, required params, and endpoint reference. Front-loaded with the core action, then logically organized.

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 2-parameter read-only tool, the description covers all necessary context: when to use, defaults, ID resolution, return shape, read-only guarantee, error semantics, and API endpoint. No gaps given the low complexity and strong annotations.

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%, so baseline is 3, but the description adds meaning: company_id defaults from config and id must resolve to an existing parent record via the list tool. This contextual guidance goes beyond the schema's simple 'URL path parameter' descriptions.

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?

Begins with 'Returns the details for a specified Company Checklist Template' — a specific verb+resource statement. It further distinguishes from list tools by noting 'when you already know which company checklist template you want and need its full field set,' which separates it from discovery-oriented siblings.

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: 'Use this when you already know which company checklist template you want and need its full field set.' It also directs the agent to resolve ID with 'the matching list tool first,' giving a clear prerequisite and referencing an alternative for discovery.

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