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

Adds genuine behavioral context beyond annotations: 'After configuring, your session reconnects automatically' discloses an important side effect the agent would otherwise not anticipate. However, annotations declare destructiveHint=true and the description never says whether existing credentials for that provider are overwritten, merged, or rejected, nor whether the operation is reversible. For a destructive write, that omission is the main gap.

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?

Three short sentences that are front-loaded with the action and provider scope, then side effects. The provider enumeration duplicates the schema almost verbatim, which is the only wasted material, but overall it is tight.

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?

An output schema exists, so return values need not be explained, and the reconnect behavior plus the AWS exclusion cover the key operational surprises. The remaining hole is what happens to previously stored credentials when this is called again, which matters because destructiveHint=true.

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 description coverage is 100%, so provider, context_id, and credentials are already documented in the schema; the baseline of 3 applies. The description restates the provider list already present in the schema and adds nothing about the credential key/value map or the context_id fallback behavior, so it contributes no semantic value over the structured fields.

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 and resource: 'Store API credentials for a provider', and enumerates the supported providers. It also carves out a scope exception (AWS is configured elsewhere), which helps an agent rule out an incorrect call. It does not name any sibling tool (e.g. ops_list_integrations, ops_remove_integration, ops_test_integration), so differentiation from siblings is left to inference.

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?

Gives clear context for when to use it (onboarding credentials for a named provider) and an explicit exclusion with a redirect: 'AWS is configured only via Admin Cloud Catalog'. It stops short of covering adjacent flows, such as verifying credentials afterwards with ops_test_integration or removing them with ops_remove_integration.

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