List Environment Variables

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

Adds the safety note about not exposing sensitive values, which is helpful, but does not disclose other behavioral traits such as error handling or read-only nature. Since no annotations exist, description carries the burden and provides minimal additional context.

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?

Extremely concise single sentence that front-loads the core purpose, with no wasted words.

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 simple list tool, the description covers the output scope (names only) but omits details about the return format, pagination, or error states, especially since no output schema is provided.

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% and the description does not explain the parameters (server_id, app_id) or how to obtain them, leaving the agent without necessary context to use the tool correctly.

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?

Clearly states the tool lists environment variable names and explicitly notes it does not expose sensitive values, distinguishing it from set-environment-variable and other related 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?

Implies usage when you need to view variable names, but no explicit guidance on when to use vs alternatives like list-cloudways-apps or set-environment-variable.

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