config_set

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

The description only says 'Update' implying mutation, but no details on side effects, persistence, or scope (e.g., whether changes are global or per-session). No annotations are provided to compensate.

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 extremely concise (one sentence), front-loaded with the verb and resource. It could be slightly more structured but is not bloated.

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 tool with 6 optional parameters and no output schema details, the description is minimal. Missing context about defaults, partial updates, or how missing keys affect state.

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?

Since schema description coverage is 0%, the description should add meaning. It merely lists parameter names already in the schema, with no additional semantics about acceptable values, format, or constraints.

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 tool updates webapp config and lists the relevant keys. However, it does not differentiate from its sibling tool 'config_get' beyond the verb 'update' vs 'get'.

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 on when to use this tool versus alternatives (e.g., when to update versus get config). No prerequisites or context about when updating is appropriate.

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