Update Custom Field Value

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

The 'CAUTION: Destructive' note adds limited value beyond the annotations, which already set destructiveHint: true. The description does not elaborate on what 'destructive' entails, nor does it mention side effects, required permissions, or the idempotent nature hinted in 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 short (two sentences) and front-loaded. The caution sentence is useful but could be more compact. Every sentence serves a purpose, though the description could be expanded to cover more context.

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 with 7 parameters and an output schema, the description is minimal. It does not explain return values, prerequisites, or how to use optional parameters, leaving gaps in completeness despite the presence of an output schema.

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 the baseline is 3. The description adds no additional meaning to parameters; it only states the tool's purpose without referencing any input specifics.

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 'Update an existing custom field value', specifying both the verb and resource. It distinguishes from sibling tools like create_custom_field_value and delete_custom_field_value.

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 implies usage for updating existing custom field values but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or context for choice are provided.

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