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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the bar is lower; the description still adds real substance about how inheritance propagates down a same-owner chain, that prior law changes remain public history, and that non-inheriting per-place permissions (building/thing/note) sit outside this call. It also enumerates rejection conditions (copy, write, wake key, convert without into_kind), which is behaviour an agent cannot get from the annotations.

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 operative sentence is correctly front-loaded, but everything after it is one undifferentiated block of tightly packed jargon with no sub-structure, so an agent must re-read to separate inheritance rules from trait-validation rules. The trailing gazette/front_door boilerplate about room #454 is unrelated to invoking this tool and dilutes the signal.

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 two-parameter, no-output-schema mutation, the description covers inheritance semantics, ownership preconditions, normalization/failure behaviour, and trait validation, which is close to what an agent needs. The remaining gap is that `place_id` is never characterised beyond ownership, and a full-replace tool never states what happens to traits omitted from the new list beyond the word "Replace."

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 carries the burden and does so for `traits`: every named trait must already exist, names are trimmed and lowercased, duplicates after normalization fail, ordering is meaningful ("ordered law traits"), and traits may use chance/reach/convert with convert requiring into_kind. `place_id` gets only indirect treatment via "a place you own," leaving the integer's resolution unchecked.

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 first sentence gives a specific verb and resource: "Replace the ordered law traits for a place you own," which tells an agent this is a full-replacement mutation on a place's law set and that ownership is required. The rest of the paragraph is dense with domain jargon (law_place, check_label, into_kind, open_to_reach) that is never defined, so the tool's identity is clear but its mechanics are opaque.

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?

It establishes a precondition ("a place you own") and one explicit exclusion ("The ownerless world accepts no laws"), and it routes to `look` for inspecting a defining place. However, it never says when to use `laws` versus neighbouring tools like `place_edit`, `thing_edit`, or `invent_kind`, so the agent must infer the boundary.

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