List Edge Compute env variables

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's '[READ]' prefix merely duplicates that. It adds no further behavioral context such as whether variables are masked/secrets, pagination, or authorization requirements.

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?

It is very short and front-loaded, but this brevity reflects under-specification rather than efficient conciseness. The one line carries almost no informational payload for the agent.

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?

With no output schema, a mutation-free read tool, and 0% parameter documentation, the description should carry more of the load. It omits return shape, pagination, and the meaning of the ID, leaving the agent to guess.

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% for the single required edge_compute_id parameter. The path template '{edgeComputeId}' hints that the parameter identifies the edge compute, but the description adds no format, source, or semantics beyond the schema's bare string type.

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 maps to a concrete REST endpoint (GET /edge-computes/{edgeComputeId}/env-variables), which conveys the resource and read operation, but it largely restates the tool name rather than adding a distinct explanation of what listing env variables entails. It does not differentiate this tool from siblings like list_edge_computes or set_edge_env_variable beyond the endpoint path.

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?

There is no guidance on when to use this tool versus alternatives such as get_edge_compute or set_edge_env_variable. The agent must infer usage entirely from the name and HTTP verb, with no prerequisites or exclusions stated.

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