ado_get_release_variables

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavior beyond these: 'Secret or unspecified secrecy values are always hidden' and 'Does not resolve variable groups or merge scopes.' These details disclose important security and scope behaviors that are not captured in the annotations, enriching the agent's understanding without contradicting the structured hints.

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 three concise sentences. The first sentence front-loads the core purpose, and the next two add critical behavioral caveats. There is no redundancy, filler, or repetition. Every sentence earns its place, making it highly efficient.

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 read-only tool with no output schema, the description covers the main scope and limitations adequately. However, it fails to explain parameter semantics (especially includeValues) and does not clarify how 'selected environment' maps to environmentId or what values each parameter expects. The description is enough for a basic call but leaves gaps that could lead to incorrect invocation, particularly around the optional parameters.

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 must compensate, but it does not. It mentions 'definition scope or a selected environment,' which hints at definitionId and environmentId, but entirely omits explanations for includeValues, project, and organization. The most ambiguous parameter, includeValues, has no description at all, leaving the agent to guess its purpose (likely controlling whether values are returned). This is a significant gap for a tool with five 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 ('Read') and the resource ('direct variables') with a specific scope ('at definition scope or a selected environment'). It is distinct from siblings like get_release_definition (which retrieves the definition itself) and list_release_environments (which lists environments). The verb is specific and resource 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 provides a clear context for what the tool reads (direct variables) and a limitation ('Does not resolve variable groups or merge scopes'), which implies situations where this tool should not be used. However, it does not explicitly name alternative tools or state 'use this when X, otherwise use Y'. The guidance is implied rather than explicit, so it falls short of a 4.

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