linux_env_variable_manager

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

The description clearly states behavioral traits beyond annotations: 'It never reads, writes, or mutates any file, environment, or host — it only transforms the text you pass in' and 'Runs locally: read-only, non-destructive, offline, contacts no external service, and is rate-limited (anonymous 30/min, 200/hr, 1000/day).' This adds context about rate limits and offline nature, supplementing the readOnlyHint, destructiveHint, idempotentHint, and openWorldHint 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?

The description is well-structured, front-loading the core purpose and then detailing operation modes and usage guidelines. However, it is slightly verbose, repeating some details that are already in the schema descriptions. Every sentence is informative, but a few could be trimmed without loss of clarity.

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 covers all necessary aspects: purpose, operation modes, parameter usage, safety guarantees (stateless, read-only, offline), rate limits, and sibling tool differentiation. Given the presence of an output schema (context: has output schema: true), the description does not need to detail return values but still explains what each operation produces.

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?

Even though schema description coverage is 100%, the description adds significant meaning by explaining how each operation mode uses the parameters. For example, it explains that 'parse' and 'audit' read the 'text' field, 'format' reads the 'input' object, and 'presets' ignores all other fields. It also describes the output of each mode, enriching the schema's enum descriptions.

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's purpose: 'Parse, audit, and format-convert a .env file' as a stateless text transform. It distinguishes from siblings by explicitly mentioning 'Use this for .env conversion and secret auditing; use linux_bash_script_generator for full shell scripts and linux_systemd_unit_generator for unit files.'

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 provides explicit guidance on when to use this tool versus alternatives: 'Use this for .env conversion and secret auditing; use linux_bash_script_generator for full shell scripts and linux_systemd_unit_generator for unit files.' It also outlines the four operation modes (parse, format, audit, presets) with their specific use cases.

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