Create Company Checklist Template Section

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate mutability but the description adds that it returns the created object on HTTP 201. However, it does not disclose side effects, required permissions, or error behavior. The description is additively useful but limited beyond 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 4 sentences. The first sentence is clear, but subsequent sentences repeat the creation intent and include an error ('Inspections' instead of 'Section'). The structure is adequate but contains redundancy and a minor inaccuracy, reducing efficiency.

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?

There is no output schema, so the description should describe the return value. It mentions 'returns the created object on success (HTTP 201)' but does not specify the object structure, constraints on name/position, or error scenarios. For a simple 4-param tool, key details are missing.

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 only lists required parameters (company_id, list_template_id) and provides the endpoint URL. It does not add semantic meaning for 'name' or 'position' beyond what the schema already provides, so no extra value.

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 it 'Creates a Company Checklist Section for a specified Checklist Template,' clearly indicating verb and resource. However, it includes an erroneous duplicate phrase 'Creates a new Inspections in Procore' which introduces confusion and slightly detracts from clarity.

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 implies usage by stating 'Use this to create a new Inspections' and lists required parameters (company_id, list_template_id). It does not provide explicit when-to-use or when-not-to-use guidance, nor mention alternatives. Among siblings, there are other section creation tools, so differentiation is implied but not explicit.

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