Create Custom Field

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false (non-destructive). The description adds that it returns the created object on success (HTTP 201) and includes the endpoint, which provides some additional context beyond annotations but does not disclose other behavioral traits like permission requirements.

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-5 sentences long, including endpoint and API version details that may be considered redundant. The first sentence captures the core purpose, but additional details could be streamlined.

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?

Given the complexity (10 parameters, no output schema), the description provides good context by explaining what Custom Fields are used for (Projects or People) and mentioning the success return. It does not explain the 'values' parameter for select types in detail, but the schema covers that. Overall, it is reasonably complete for a creation tool.

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?

The input schema has 100% description coverage for all 10 parameters. The description adds minimal parameter semantics beyond listing required parameters, which are already marked as required in the schema. Thus it does not significantly add meaning 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 new Custom Field for a given company ID and explains what Custom Fields are. It distinguishes the action from related siblings like update_custom_field and delete_custom_field implicitly through the verb 'create', but does not explicitly contrast them.

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 context on when to use this tool ('Use this to create a new Custom - Configurable Tools in Procore') and lists required parameters (company_id, name, type). However, it does not specify when not to use it or mention alternatives such as update_custom_field.

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