set_runtime_config

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

Without annotations, the description must disclose behavioral aspects. It reassures that no SSH passwords or secrets are stored, which is good. However, it does not mention whether it overwrites existing config, requires a restart, or persists across sessions. These are critical for a mutation 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 concise with two sentences. The first sentence clearly states the purpose, and the second adds a security reassurance. No unnecessary text. It is well-structured and front-loaded.

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?

Given the complexity of a persistence operation and the absence of an output schema, the description is incomplete. It does not describe return values, error conditions, or the effect on the system state. The schema provides some parameter descriptions, but the tool's overall behavior is under-specified.

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 75%, but the tool description adds minimal semantic value beyond the schema. It mentions 'Python or Conda runtime' but does not explain the mode enum values or when to use each parameter. The security note about not storing secrets is peripheral to parameter usage.

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 it persists the local Python or Conda runtime used to start server.py. The verb 'persist' indicates a write operation, and it distinguishes from the sibling runtime_config_status which likely reads the config. However, it could be more explicit about setting/updating the config.

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?

No guidance is provided on when to use this tool versus alternatives like runtime_config_status. It does not mention prerequisites, when persistence is needed, or how it interacts with other tools.

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