update_mcp_integration_workspaces

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

Annotations indicate readOnlyHint false (writes) and openWorldHint true. Description adds that changes take effect immediately for all users in selected workspaces, which is valuable beyond annotations. It does not cover rollback or idempotency, but annotations already handle safety hints.

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 front-load the purpose and key behavioral note. No redundant or extraneous text. Every sentence serves a clear purpose.

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 covers the action, recommended preceding step, and immediate effect. With an output schema present (though not shown), the description is adequate. Lacks details about error cases or prerequisites but is complete for the tool's complexity.

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?

Input schema has 100% description coverage, so baseline is 3. The description mentions 'bulk' which hints at the array structure but does not add significant meaning beyond the schema. Parameter names and descriptions in schema are already clear.

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 tool grants or revokes workspace access to an MCP integration in bulk, which is a specific verb-resource combination. It distinguishes itself from siblings like list_mcp_integration_workspaces by referencing the need to review current state first.

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?

Explicitly advises using list_mcp_integration_workspaces first to review current access, providing clear context for when to use this tool. However, it does not mention alternatives or situations where this 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.