get_variables

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is known. The description adds valuable context beyond annotations: the required stopped state, paging support, and a note about the escape hatch. It does not repeat the 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 concise and front-loaded with the purpose. It uses a clear structure: brief intro, state requirement, paging mention, parameter details, escape hatch. Every sentence adds value without redundancy. It is not overly verbose.

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?

Given no output schema, the description covers the essential aspects: what the tool does, preconditions, paging, and parameter meanings. It could be improved by describing the return format (e.g., an array of variable objects), but the current level is sufficient for an agent to understand usage.

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 description coverage is 0%, so the description carries the full burden. The 'Args:' section explains each parameter (variables_reference, filter, start, count) with meaningful descriptions, including the allowed values for filter ('indexed' or 'named'). This adds significant value beyond the bare schema.

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 'Get variables for a scope or structured variable,' which is a specific verb and resource. It distinguishes itself from siblings like get_scopes (which returns scopes) and set_variable (which modifies) by mentioning the prerequisite call to get_scopes and the stopped state requirement.

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 'State: STOPPED required. Call get_scopes() first to get variables_reference,' providing clear when-to-use guidance and a prerequisite. It could improve by explicitly contrasting with set_variable or other alternatives, but the context is sufficient for an AI agent.

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