update_app_instance_config

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Update only the configuration', indicating mutation. However, it omits details on idempotency, side effects, or response behavior. The merge behavior is hinted in the schema for the 'config' parameter but not in the main description, thus failing to add sufficient behavioral context.

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?

The description is a single concise sentence with no waste. It is front-loaded with the key action and scope. However, for a tool with five parameters and potential behavioral nuance, it could be slightly more informative while remaining concise.

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 the tool's complexity (mutation with no output schema, no annotations), the description is insufficiently complete. It does not describe what happens after a successful update, error conditions, or prerequisites like required permissions. The phrase 'only the configuration' adds some context but leaves major gaps.

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 the baseline is 3. The description adds no additional meaning beyond the schema; it does not elaborate on any parameter. Each parameter's purpose is adequately described in the schema, so no penalty.

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 'Update' and the resource 'configuration of an installed app instance', with 'only' specifying the scope. This distinguishes it from the sibling tool 'update_app_instance' which likely updates other fields. However, it does not elaborate on what 'configuration' encompasses.

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 description implies use when only updating configuration (vs. other attributes) but provides no explicit guidance on when to use this tool versus alternatives like 'update_app_instance' or when not to use it. No usage context or prerequisites are given.

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