Create a custom field

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so the safety profile is covered. The description adds one piece of context, 'Changes account configuration', which signals account-level mutation, but it says nothing about the confirm parameter, permission requirements, or side effects of creating a field.

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?

Two short, front-loaded sentences with no wasted words. It is efficient, though the first sentence largely restates the title rather than earning extra information.

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?

Annotations cover the safety profile and no output schema is needed, but for a create tool with a confirm gate and a nested payload object, the description should do more to explain what a custom field is and any required setup. It is minimally adequate rather than complete.

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 description coverage is high (80%), so the schema carries most of the parameter meaning, including the account, confirm, payload, and payload_file descriptions. The description adds no parameter-level detail beyond what the schema already provides, matching the baseline for well-documented schemas.

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 a specific verb and resource ('Create a custom field'), which is clear and actionable. However it does not distinguish this from siblings like bulk_create_custom_fields or update_custom_field, so an agent gets no help choosing between them from the text alone.

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?

There is no indication of when to use this tool versus bulk_create_custom_fields, update_custom_field, or list_custom_fields, and no prerequisite or exclusion information. Usage must be inferred entirely from the tool name.

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