integration_config

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

Annotations already declare readOnlyHint=true, idempotentHint=true and non-destructive, so safety is covered. The description adds the useful exclusion of install/start/approve side effects, which reinforces behavior beyond annotations. It does not describe the generated artifact form or whether it's returned inline vs written to disk, so with annotations present a 3 fits.

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?

A single tight sentence plus a negative clause; no filler. Front-loads the two output modes before the exclusion, which is the right order.

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 output schema presumably documents the return shape, and annotations give the safety profile, so the remaining gap is parameters and the branch condition distinguishing the AWS-server config from the remote Knowledge config. For a 3-required-param generator with two modes, the description leaves too much unstated.

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 0% and all three parameters are required, so the description carries the full burden. It never mentions serverId, awsProfile or region, nor their formats, defaults or the difference between the local-AWS path and the remote Knowledge path. Anonymous params make correct invocation harder.

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 the resource (a version-pinned local config for an official AWS server, or a remote Knowledge config) but the verb is fuzzy: 'Generate' doesn't say what artifact or output is produced beyond 'configuration'. Sibling tools like integration_catalog and mcp_config_review are adjacent, and nothing distinguishes this tool from them.

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 negative scope ('Does not install, start or approve tools') gives an implied when-not, but there's no explicit when-to-use or comparison against integration_catalog or mcp_config_review. An agent must infer selection from sibling names alone.

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