Create Company Checklist Template

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

Annotations already indicate non-destructive, non-idempotent behavior. The description adds that it returns HTTP 201 on success, but does not disclose side effects, permissions, or rate limits. No contradiction with 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?

Description is three sentences, reasonably concise, and includes the endpoint. However, the second sentence is confusing and could be removed to improve front-loading.

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 tool creating a complex object (checklist template), the description lacks details about template structure, formatting of 'list_template', or return values. No output schema exists to compensate.

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 description adds little to parameter understanding. It repeats that 'company_id' and 'list_template' are required but does not explain the structure of 'list_template' or 'attachments' 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 clearly states it creates a Company Checklist Template for a specified company, and distinguishes from siblings like 'create_company_checklist_template_section'. However, it inaccurately says 'Use this to create a new Inspections in Procore', which could confuse.

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 provides no guidance on when to use this tool vs. alternatives like 'create_checklist' or 'create_checklist_inspection'. It only lists required parameters but lacks context for decision-making.

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