configure

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

Discloses that only non-empty arguments are applied and that loading new SVD/ELF takes effect on next use. No annotations to contradict. Could mention persistence across sessions.

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?

Concise, well-organized with clear parameter explanations. No fluff; every sentence adds value.

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?

Covers all parameters and behavior for a configuration tool. Output schema exists so return value explanation is unnecessary; could mention if settings persist.

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 coverage is 0%, but description compensates with detailed, example-filled explanations for each parameter, including specific usage guidance for 'transport'.

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?

Clearly states verb 'set' and resource 'chip/project settings for this session'. Distinguishes from sibling tools like 'connect', 'flash_write' by focusing on configuration.

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?

Provides explicit behavior (only non-empty arguments applied) and alternative (openocd-mcp.json file). Lacks explicit when-not-to-use but context is clear.

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