mcp_terminal_get_config

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

With no annotations provided, the description carries the full burden. It discloses that the password is shown once, the ZIP is base64-encoded, and the Anthropic key is optionally included. It does not specify potential side effects or permission requirements, but the key behaviors are well covered.

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 three sentences long, front-loaded with the main purpose. It is well-structured but contains a somewhat lengthy sentence about the setup wizard path. Every sentence adds value, though brevity could be slightly improved.

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 moderate complexity (3 parameters, no output schema), the description covers the purpose, output format (base64 ZIP + temporary password), and how to apply the config. The 'connection' parameter is not addressed, but overall the information is sufficient for an agent to invoke the tool correctly.

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 67% (two of three parameters have descriptions). The description clarifies 'tenant_code' as an override for the caller's db/alias and 'include_anthropic' for embedding the key. The 'connection' parameter defaults to 'default' but is not explained in the description, leaving a gap.

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 explicitly states the verb ('generate'), the resource ('password-protected ZIP archive with Claude Terminal configuration keys'), and the scope ('for the requesting tenant'). It clearly defines what the tool does, distinguishing it from the unrelated sibling tools.

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 explains when to use the tool: to generate config for applying via the Odoo Setup Wizard. It also notes that the Anthropic key is excluded by default, guiding parameter choice. However, it does not explicitly discuss alternatives or situations where the tool should not be used.

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