Get published variables

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral context beyond that: it is a raw REST endpoint, omits valuesByMode, and requires Enterprise plan plus file_variables:read permission. This is meaningful transparency for a read-only API call.

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 extremely compact: endpoint, key behavioral caveat, auth requirement, and preferred alternative are all packed into one short string. Every fragment earns its place and the endpoint is front-loaded.

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 one-parameter read-only tool with no output schema, the description covers the essentials: what it returns, what it does not include, required permissions, and the preferred sibling. It is slightly terse about the overall response shape, but adequate for selection and invocation.

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 only parameter, file, is fully described in the input schema (100% coverage), so the description does not need to compensate. The URL template merely repeats the same parameter without adding new semantic meaning, so baseline 3 is appropriate.

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 names the exact endpoint and states the resource and behavior: raw REST published variable names without valuesByMode. It also distinguishes the tool from the sibling get_variable_defs by pointing to the preferred alternative, so an agent can tell them apart.

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 explicitly says 'Prefer get_variable_defs.' That gives an alternative and a clear preference signal. It does not fully spell out the conditions under which this raw REST endpoint should be used instead, but the 'raw REST' and 'no valuesByMode' qualifiers imply when this tool is appropriate.

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