Update experimental instance settings

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

Annotations already indicate readOnlyHint=false (modifying) and destructiveHint=false. The description adds only the HTTP method (PATCH) and authorization class, which are minimal. It does not disclose behavioral traits like immediate effect, partial update nature, or whether changes persist.

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 very short (two sentences), but it omits essential parameter details and usage context. It is concise at the expense of completeness, making it less helpful for an AI agent.

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 complexity (24 boolean fields in a nested object) and the presence of an output schema, the description lacks completeness. It does not explain the purpose of each setting, the effect of updates, or the request/response format. It barely qualifies as minimally viable.

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%, so the description must compensate, but it provides no information about the 'body' parameter or its many properties. The agent must rely solely on the schema, which lists boolean names without explanations. This is a critical gap.

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 'Update experimental instance settings' with a specific verb and resource, distinguishing it from sibling tools like pc_get_instance_settings_experimental (read) and pc_patch_instance_settings (update non-experimental). However, it could explicitly contrast with these siblings.

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?

No guidance on when to use this tool instead of alternatives. It does not mention prerequisites, when not to use it, or that reading experimental settings should use pc_get_instance_settings_experimental. The description lacks any usage context.

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