edit_variable

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false. Description adds 'Idempotent' and 'Modifies in place,' but these are redundant with annotations. No additional behavioral context like required permissions, side effects, or error states disclosed.

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?

Description is somewhat verbose with emoji, HTTP path, and repeated phrases like 'Edit a Variable' and 'Edit a personalization variable.' Could be streamlined to a single clear sentence.

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?

Tool has a nested object parameter and no output schema. Description does not explain the response behavior or error conditions. Schema covers parameters but the description lacks operational context.

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?

Both parameters have 100% schema description coverage, so the schema already explains them. Description adds no further parameter-specific meaning beyond the schema's field-level descriptions.

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?

Description clearly states the tool edits/modifies a variable (personalization) with 'Edit a Variable' and 'Modifies an existing record in place.' The HTTP path and entity name 'Personalizations' make the resource explicit. Distinguishes from create_variable and delete_variable among siblings.

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?

Description implies use when updating an existing variable due to 'Modifies an existing record in place.' Lacks explicit guidance on when to use this tool vs alternatives like create_variable or other update tools. No 'when-not' or prerequisite conditions stated.

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