create_catalog_item_variable

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

With no annotations provided, the description should disclose behavioral traits such as mutating effects, potential errors, or validation requirements. The description only states the action without any behavioral details. It does not mention permissions, idempotency, or consequences. This is a significant gap for a mutation tool.

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 a single sentence that succinctly states the tool's purpose with no fluff. It is front-loaded with the primary action and resource. However, it is perhaps too terse given the tool's complexity, though conciseness itself is not penalized.

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 14 parameters, no output schema, and no annotations, the description is severely incomplete. It lacks information about how to use the tool effectively, what the expected inputs are, or what happens after creation. The description provides no context beyond the basic purpose, which is insufficient for an agent to call this tool correctly without additional inference.

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 description does not elaborate on any parameters. The input schema has only 36% description coverage, leaving many parameters (max, min, order, help_text, mandatory, max_length, default_value, reference_qualifier) undocumented. The description does not compensate for this gap, providing no guidance on required vs optional fields or relationships between parameters.

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 (a new variable/form field on a catalog item). While it doesn't explicitly name sibling tools, the verb and object differentiate it from list/update operations. The purpose is unambiguous.

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 the tool is for adding new variables, but provides no explicit guidance on when to choose this over update_catalog_item_variable or list_catalog_item_variables. No alternative tools are mentioned, and no conditions are given. Usage is only implied by the word 'Create'.

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