Show Company Checklist Section

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

Annotations already provide readOnlyHint/idempotent/destructive hints, and the description adds useful context: error status codes (401/403/404), return type, endpoint, and company_id default. It restates read-only behavior but this is in plain language and reinforces the annotation.

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 a single dense paragraph but well-structured, beginning with purpose, then usage, return, errors, and endpoint. Every sentence carries value, though it is longer than the two-sentence ideal and includes redundant read-only confirmation.

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 GET, it covers purpose, prerequisites, return type, error behavior, and endpoint. Lacks detail on the exact fields returned, but with no output schema, the description provides enough for an agent to invoke the tool 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 coverage is 100%, so baseline is 3. The description adds meaning by stating id must identify an existing parent record and that company_id defaults to procore_set_config, though the default note conflicts with the schema's 'required' flag. This ambiguity prevents a 5.

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 'Returns the details for a specified Company Checklist Section' with a specific verb and resource, and distinguishes from the list tool by saying 'Use this when you already know which company checklist section you want and need its full field set.' This clearly separates it from sibling list/show tools.

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 explicitly says when to use the tool ('when you already know which company checklist section you want') and instructs to resolve id with the matching list tool first. It also notes the company_id default behavior. It lacks an explicit 'when not to use' but the guidance is strong enough.

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