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

Annotations already declare this operation as destructive, idempotent, and not read-only, so the safety profile is largely covered. The description adds no behavioral context beyond the name—it does not explain that schema_content replaces the full definition, what happens to existing data or versions, or how compatibility checking behaves.

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 clear sentence with zero wasted words, and the core action is front-loaded. Its brevity is appropriate structurally, though it leaves important behavioral context unstated.

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?

For a destructive mutation with a nested object parameter and no output schema, the description is too sparse. It omits key context such as whether the update is a full replacement or a partial patch, how compatibility checks affect behavior, and what the operation returns or affects when it fails.

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 input schema already documents all four parameters, including the required schema_uuid and schema_content and the optional new_version and check_compatibility. The description adds no parameter-level semantics beyond what the schema provides, which is the baseline for full schema coverage.

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 states a specific verb ('Update') and resource ('an existing schema definition'), making the basic operation clear. However, it does not differentiate this tool from closely related siblings such as schema_save or schema_validate, so an agent must infer when this is the right choice.

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 provides no guidance on when to use this tool versus alternatives like schema_save or schema_validate, and it does not mention prerequisites, exclusions, or expected contexts. Usage must be inferred from the name alone.

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