retrieve_variable

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds confirming context ('Fetches data. Makes no changes to your ActiveCampaign account.') and specifies the HTTP method and path, but does not significantly expand beyond what annotations provide.

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 relatively concise, though it repeats the title 'Retrieve a Variable' within the body. The inclusion of the emoji and endpoint adds useful structure without excessive verbosity.

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 simple single-retrieve tool with one required parameter and no output schema, the description adequately conveys purpose, safety, and required input. It could mention return format, but given common patterns and annotations, it is sufficiently 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 coverage is 100% with the variableID parameter already described as 'ID (int) of variable'. The description does not add additional semantic detail about the parameter beyond what the schema provides.

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 tool retrieves a single personalization variable. It uses specific verb ('Retrieve') and resource ('Variable'), and the use of 'individual' distinguishes it from listing operations like 'list_variables'.

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 provides clear context ('READ-ONLY', 'Personalizations', 'GET /personalizations/{variableID}') and indicates the tool makes no changes. It implicitly communicates that it is for fetching a single variable by ID, though it does not explicitly exclude alternatives like list_variables.

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