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

The annotations already signal destructiveHint=true, but the description goes far beyond that by explaining the dry-run default, the approval-before-persist workflow, the no-LLM-call constraint, and the publish_schema dependency. It also discloses nuanced transformation behavior such as compact scalar occurrences becoming shared $defs references and host_path/strip_prefix not applying to that form. No contradiction with annotations exists.

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 dense but every sentence earns its place: behavior, special cases, workflow, constraints, and references are all covered without repetition. The most important operational detail (dry_run default and approval requirement) is placed near the end but is clearly highlighted, and the overall structure is logical.

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 complex transformation tool with five parameters, an output schema, and destructive annotations, the description covers all critical aspects: what gets moved, how names change, edge cases, the safe execution workflow, permissions, and downstream dependencies. The output schema exists, so return-value details need not be repeated in the description.

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?

Although schema coverage is 100%, the description adds substantial meaning beyond the schema: it enumerates valid host_path forms, clarifies when strip_prefix applies, explains that compact scalar occurrences are converted to shared references, and ties region_id to get_schema's x-entityMap. This materially helps an agent choose correct parameter values.

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 ('Materialize') and resource ('an entity region from get_schema's x-entityMap'), and goes on to explain exactly what materialization means: moving flat members into a new object, nesting child regions, and stripping prefixes. This clearly distinguishes it from generic schema-editing siblings like update_schema or move_schema_property.

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 gives strong usage context: it requires editor access, makes no LLM call, defaults to dry_run, and requires approval before persisting. It also notes that database-linked structural edits still require publish_schema, providing a clear when-not-to-use boundary. It does not name an explicit alternative tool for the same operation, but the context is sufficient for an agent to route correctly.

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