list_application_envs

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

The description indicates a read-only operation (list), which is non-destructive. However, no annotations are provided, so the description carries the full burden. It does not disclose potential side effects, authentication requirements, or output format. For a simple list tool, this is adequate but not exceptional.

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 two sentences long, no wasted words, and front-loads the key action. It is efficient and to the point.

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 one-parameter list tool with no output schema, the description covers the basics. However, it does not describe the return format or any edge cases (e.g., empty list, pagination). Minor gaps in completeness.

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?

The input schema covers 100% of parameters, providing descriptions in the schema. The description adds value by specifying how to obtain the uuid parameter ('Get this from list_applications'), which helps the agent 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?

The description explicitly states 'list all environment variables for a specific application', which clearly identifies the verb (list) and resource (environment variables for an application). It distinguishes from sibling tools like create/delete/update operations and bulk operations.

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 includes 'Use this to view current environment configuration', which provides clear guidance on when to use this tool. While it doesn't explicitly mention when not to use it, the sibling tool set implies different use cases.

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