List environment variables

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it calls GET /services/{serviceId}/env-vars, confirming it's a read operation. It does not disclose pagination behavior or rate limits, but the schema provides pagination params. Overall, adequate beyond 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?

Two sentences with the key action first. No redundant words. Efficient and front-loaded with the purpose.

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?

The description does not mention the return value or response structure. Although no output schema is provided, for a list tool it would be helpful to indicate what fields are returned (e.g., list of environment variable objects). This is a notable gap.

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 each parameter having a description. The description adds no further meaning beyond restating that serviceId is needed. Baseline 3 applies as schema handles semantics completely.

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 lists environment variables for a specific service, using a specific verb ('List') and resource ('environment variables'). It distinguishes from sibling list tools by focusing on env vars and requiring a service ID, which is unique among list tools.

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 does not provide when-to-use or when-not-to-use guidance, nor does it mention alternatives. It is straightforward, but lacks explicit usage context relative to siblings like 'render_list_secret_files_for_service' or 'render_update_env_vars_for_service'.

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