createCustomField

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

No annotations are present, so the description carries the full burden of behavioral transparency. The phrase 'Create a custom field' only implies a write operation but does not clarify side effects, permissions required, uniqueness constraints, or whether dropdown options are required for certain types.

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 extremely concise with no wasted words, fitting the tool's simplicity. It is front-loaded, but it is a phrase rather than a full sentence, which slightly reduces clarity.

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 lack of annotations and output schema, the description leaves out critical context such as the entity type (person, deal, etc.) the custom field belongs to, uniqueness expectations, and how it relates to sibling tools like createDealCustomField. This is insufficient for an agent to safely select and invoke the tool among many similar create operations.

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 covers all parameters (100% coverage) with descriptions for each, so the description does not need to add parameter semantics. The schema already explains 'name', 'type', and 'options', and the description adds no extra meaning beyond that.

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 the action (create) and the resource (custom field), making the core purpose unambiguous. However, it does not differentiate this tool from the sibling 'createDealCustomField', which might also create a custom field but for deals specifically.

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?

No guidance is provided on when to use this tool versus alternatives like createDealCustomField or updateCustomField. There are no indications of prerequisites, target entity (e.g., person vs. deal), or scenarios where this tool is appropriate.

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