load_conda_env

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

With no annotations, the description carries the full behavioral burden. It discloses the launch-context trigger but says nothing about side effects: whether existing environment variables are overwritten, whether the change persists for the session or affects other running tools, or whether it can fail when the env does not exist.

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?

Two sentences, zero waste, with the action front-loaded and the usage condition immediately after. Nothing needs trimming.

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 one-optional-param, no-output-schema tool the description is mostly adequate, but it omits whether the load is session-scoped or permanent and what happens on failure. Those gaps matter for a tool that mutates the server's process environment.

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 100% and the single env_name parameter is fully documented with its type and default, so the schema does the heavy lifting. The description adds no format or naming conventions beyond what the schema already 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?

States a specific verb+resource: loading environment variables from a conda environment. The action is unambiguous and implicitly distinct from sibling read tools like get_conda_env_status and list_conda_envs, but it never names those siblings or explicitly contrasts itself with them.

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?

Gives a clear triggering condition: use when the MCP server is launched from a desktop app (like Zed) without the conda environment pre-activated. That implies the when-not case (conda already active), but no alternative tool or recovery path is named for those other scenarios.

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