ecp_system_set_config

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

With no annotations, the description must carry the behavioral burdenags. It says 'Update' which implies a write operation, but it does not warn about potential side effects (e.g., configuration changes may break ECP), does not state that the confirmation flag is required, and gives no sense of irreversibility. A cautious agent would need more transparency.

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, concise sentence with no fluff. It front-loads the action and object. However, it is so brief that it misses opportunities to add value; it is efficiently written but not maximally informative. Still, it earns points for being free of redundancy.

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 no annotations and no output schema, the description should provide context about return values, side effects, or example use cases. It does not. The tool modifies a configuration endpoint; knowing what happens to existing configs or how this interacts with other settings would be important for an agent to use it safely.

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?

The schema describes two parameters, but the description only hints at 'config' (key/value pairs) and says nothing about 'confirm'. The confirm parameter is a boolean constrained to true, which is not explained. Since schema coverage for parameter descriptions is 0%, the description carries full burden and fails to explain the semantics of each field.

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 the action ('Update') and the target ('ECP config key/value pairs'). It's specific enough to distinguish from related tools like ecp_storage_bd_set_config, though it doesn't explicitly mention the tool name's 'system' scope. The verb and object are clear, so an agent can infer this is a mutation of ECP-level configuration, not storage 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?

There is no guidance on when to use this tool versus alternatives, nor any context about prerequisites or typical scenarios. The description simply states what it does without saying when to invoke it. In a large tool set with many similar setters, this lack of differentiation is a weakness.

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