env

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

With no annotations provided, the description carries the full burden of disclosing behavior. It reveals that variables matching secret patterns are automatically hidden from LLM responses and that files are stored at a specific path. These are meaningful behavioral details that a user would need to know, though it does not mention side effects like deletion permanence.

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 short paragraphs, front-loaded with the core purpose. Every sentence provides useful information: the main function, secret detection behavior, and storage location. There is no redundant phrasing or filler.

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 tool has an output schema, so return values are already covered. The description supplies important context about secret handling and file storage. It does not address error cases or operation-specific effects, but for a tool of this complexity (6 params, 5 operations) it is reasonably complete.

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?

All parameters are described in the schema (100% coverage), so the baseline is 3. The description adds little direct parameter context, but it does explain the secret detection patterns that relate to variable keys. However, it does not elaborate on operation-specific parameter usage beyond what the schema provides.

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 states the tool 'Manage environment variables', clearly identifying the resource and function. It distinguishes from sibling tools (nodes, relationships, execute, query) by focusing on environment variables. However, 'manage' is somewhat generic and does not enumerate the specific CRUD operations, though the schema's operation parameter clarifies this.

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 any guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions. The description only states what it does, not when it should be preferred over other tools.

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