manage_env

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

No annotations exist, so the description carries the full burden. It does disclose the mutation semantics (set modifies .env, unset removes a key) and the side-effect nuance that unset falls back to auto-discovery. A note that writes persist to disk and affect future CLI runs would have pushed this to 5, but the disclosure is clear.

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?

Front-loaded with the core purpose in the first sentence ./tight bullet structure groups keys (with their semantic role) and actions (with default and side-effects) separately. Every bullet earns its place; no 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?

For a 3-parameter tool with no annotations and no output schema, the description covers the action enum semantics, the meaning of each key, the default action, the value requirement, and the side-effect of unset. The list action's output is addressed ('show all settings, configured values'). It is adequate, and the only real gap is not explicitly detailing the set action's confirmation behavior on success.

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 high (>80%: action enum, key enum, value), so the baseline is 3. The description adds real value by explaining what each key is for (speaker detection, auto-discovery fallbacks for the two CLI paths) and the constraint that the path must exist for PODCLI_*_PATH keys. This meaning goes beyond the raw schema, so a 4 is earned.

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?

Opens with a precise statement of scope — 'List, set, or unset global podcli settings stored in .env' — then enumerates exactly which keys the tool manages and what each key is for. An agent can disambiguate this tool and understand its purpose without opening the schema.

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?

Each action is defined, the default is stated ('list' is implied as default), and the two conditional behaviors are spelled out: 'set requires path to exist for PODCLI_*_PATH keys' and 'unset falls back to auto-discovery'. The guidance is concrete and actionable.

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