create_mcp_integration

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

Annotations already indicate it's a write operation (readOnlyHint=false) and not destructive. Description adds behavioral context: registers connection, returns id/slug, and conditional requirement for custom_headers. No contradiction with annotations.

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 succinct sentences: first states core action, second adds conditional and follow-up. No redundancy, front-loaded with essential info.

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 complexity (8 parameters, nested objects, enums), the description covers purpose, conditional requirement, and next steps. However, it omits the context that workspace_id is required when using org admin keys, which is relevant for some users. Output schema exists, so return format is covered elsewhere.

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 100%, so baseline is 3. Description adds value by explaining the conditional requirement for custom_headers when auth_type is headers, which is not in the schema's description. Also hints at output (id and slug).

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?

Clearly states it creates an MCP integration from an external URL, registers the connection, and returns id and slug. Distinguishes from sibling create_mcp_server by focusing on integration registration.

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 conditional guidance (custom_headers required for auth_type=headers) and suggests follow-up steps (create_mcp_server and capability updates). Does not explicitly state when to use this over alternatives, but context is clear.

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