Set LDAP configuration on a DrayTek Vigor 3912S router, requiring user confirmation before applying changes.
Configure LDAP (write — requires confirmation)
| Name | Required | Description | Default |
|---|---|---|---|
| param | Yes | ||
| user_code | No | ||
| confirm_token | No | ||
| confirmation_id | No |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The confirmation disclosure adds value, but the description is still thin on behavioral detail.
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?
Brevity is not an asset when the description omits required meaning.
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?
The description provides a minimal starting point but not enough context for an agent to call this tool confidently.
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?
There is a partial hint toward confirm_token and confirmation_id, but the description falls far short of clarifying the parameter semantics.
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?
It conveys a write action on LDAP, which separates it from read-only LDAP siblings, but not precisely enough to guide selection beyond that broad contrast.
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 intended usage is only weakly implied by the word 'configure' and the confirmation note, not stated as actionable guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.