Set startup variable

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

No annotations are provided, so the description must carry the full behavioral burden. It states that a value is set, but it does not disclose whether this overwrites existing variables, requires a restart, needs specific permissions, persists changes, or what side effects occur.

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 a single front-loaded sentence with no redundant or filler text. It is concise and structurally efficient, although the same brevity contributes to gaps scored under other dimensions.

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 mutation tool with seven parameters, no annotations, and no output schema, this description is not complete enough. It omits prerequisites, alternatives, side effects, and any indication of what happens after the startup variable is set.

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 description coverage is only 57%, and the description does not explain any of the seven parameters. In particular, the required server, key, and value parameters lack schema descriptions, and the description does not clarify their syntax, constraints, or relationship to the startup environment.

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 gives a specific verb and resource: 'Set the value of a startup environment variable.' It is clear what the tool does, but it does not distinguish this from the sibling server_startup_get or clarify scope, such as whether it creates new variables or only updates existing ones.

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?

There is no explicit guidance on when to use this tool versus alternatives such as server_startup_get, nor any prerequisites or exclusions. The verb 'Set' implies mutation, but the description offers no situational guidance beyond that implication.

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