sassy_env_set

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

No annotations are provided, so the description carries the full burden. It discloses two key behavioral traits: persistence for the lifetime of the server and no modification to system env. This is valuable context beyond just 'set env var' and covers the main side effects for this simple tool.

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 sentences, front-loaded with the primary action. Every sentence earns its place: purpose, persistence scope, and guidance for permanent changes. No redundancy or fluff.

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 2-parameter tool with an output schema, the description covers purpose, lifetime, and scope, and even points to alternatives. It lacks minor details like overwrite behavior or validation, but these are not critical given the tool's simplicity and the presence of an output schema.

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 0%, so the description must compensate for parameter meaning. It implicitly identifies 'name' as the environment variable and 'value' as its value via the verb 'set an environment variable', but adds no extra semantics (e.g., constraints, format, overwrite behavior). The property names are self-explanatory, so the description adds marginal value beyond the schema.

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 'Set an environment variable for the current SassyMCP process' with a specific verb and resource. It distinguishes from sibling tools like sassy_env_get and sassy_env_list by emphasizing the 'set' action and the process-local scope.

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?

Provides clear usage context: persists for the server lifetime and does not modify system env. Explicitly suggests registry or system settings for permanent changes, giving an alternative. Could more explicitly say 'use this for temporary process-scoped env settings' but the intent is clear.

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