configure

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

The description details actions and available settings, disclosing behavioral traits such as the effect of 'set' action. It does not mention persistence or side effects, but this is acceptable for a configuration tool. No annotation contradiction.

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 well-organized into Args, Available settings, Examples, and Returns. It is concise yet complete, with no wasted sentences.

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 three simple parameters, zero schema coverage, no annotations, and an output schema, the description thoroughly covers purpose, parameters, settings, and examples. It adds necessary context for correct tool invocation.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning—action as 'view' or 'set', key as config key, value as new value—and listing all configurable settings. This goes well beyond the raw 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 'View or update Code Mode configuration', providing a specific verb and resource. This distinguishes it from sibling tools like run_python or pip_install, which focus on execution or installation.

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?

The description explicitly indicates when to use 'view' vs 'set' actions. It does not explicitly state when not to use or mention alternatives, but the context of sibling tools makes the usage clear.

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