Update a client tunnel preset

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

Annotations already cover safety (readOnly=false, destructiveHint=false, idempotentHint=true), so the description is not required to repeat those. It adds the scope of 'authenticated user's presets' and mentions updating name or config. However, it does not disclose whether the config array is replaced entirely or merged, nor any auth requirements beyond the implied user scoping.

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?

Two sentences with zero waste, purpose stated upfront. The description is appropriately concise and front-loaded with the core action.

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 tool has a complex config array with nested objects, 5 parameters, and no output schema. The description is minimal and does not explain how to construct the config, what platform/computerName mean, or what the return value is. For an update operation, this is insufficiently complete.

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 only 20% (only the config array has a description). The tool description mentions 'name or config' but does not explain platform, computerName, or the structure of config beyond what the schema provides. With low coverage, the description should compensate but does not.

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?

States a specific verb+resource (update client tunnel preset) and clarifies the scope (name or config of authenticated user's presets). It is clear what the tool does, but does not explicitly differentiate from sibling tools like create or list beyond the verb.

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 implies usage for modifying an existing preset, but does not provide explicit when-to-use guidance or exclusions. It does not mention alternatives like create_client_tunnel_preset or list_client_tunnel_presets, so the agent must infer context.

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