Create Company Form Template

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

Annotations indicate readOnlyHint=false (write operation), destructiveHint=false, idempotentHint=false. The description mentions HTTP 201 on success and hints at multipart/form-data for fillable_pdf, but doesn't elaborate on error behavior, rate limits, or other side effects. It does not contradict 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 two sentences plus required parameter list and API info. It is relatively concise but has slight redundancy ('Create a new Company Form Template' and 'Use this to create a new Forms in Procore'). Front-loads key information effectively.

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 3 required params, no output schema, and annotations present, the description covers basic creation details and response status. However, it lacks explanation of the form_template object structure, prerequisites, or return value structure. Adequate but not comprehensive.

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% and descriptions for parameters are already detailed. The description lists required parameters and mentions multipart/form-data for fillable_pdf, but adds no new semantic meaning beyond the schema. Baseline 3 applies due to high schema coverage.

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 'Create a new Company Form Template' and specifies it creates a new Form in Procore, with the endpoint and HTTP 201 response. This distinguishes it from sibling tools like 'create_form' (which creates a form instance) and 'update_company_form_template'.

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 says 'Use this to create a new Forms in Procore' and lists required parameters, but provides no guidance on when not to use it, prerequisites, or alternatives. Given the large sibling list with many creation tools, clearer delineation is needed.

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