update_mcp_server_capabilities

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

Discloses that changes take effect immediately and override integration-level settings. This adds behavioral context beyond annotations (readOnlyHint=false, openWorldHint=true). No contradictions.

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, no superfluous words. Key information is front-loaded: verb, effect, and prerequisite 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?

With full parameter schema coverage and an output schema present, the description adequately complements the structured data. All necessary context is provided for correct 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?

Schema covers 100% of parameters with descriptions. The description does not add extra meaning beyond the schema; baseline 3 applies.

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 the verb 'Enable or disable' and the resource 'capabilities on an MCP server'. It distinguishes from sibling tools like update_mcp_server and update_mcp_integration_capabilities by focusing on capability toggling.

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 guidance to first inspect current surface using list_mcp_server_capabilities, and explains that changes override integration-level settings. Explicitly advises when to use it, though could mention when not to.

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