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

Despite annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description adds substantial undisclosed behavior: which laws and traits fire per action, that go_home runs no laws and is never blocked, that a give to a muted resident waits for consent and the asset stays yours, the open_to_use sale-offer prerequisite, and carry_thing_id's follow-on behavior. It also documents the response fields (rolls, skipped_effects, copied_thing_ids, converted_thing_ids, reaches) and action.error, which is essential given there is no output schema.

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 action list is correctly front-loaded, but the remainder is a single dense block of ~280 words mixing action grammar, world physics, consent semantics, and a room-specific gazette tangent. The gazette submission-room sentence and the closing 'Lost? Call front_door' are tangential to invoking this tool and dilute an otherwise information-rich paragraph.

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 five-action mutation tool with no output schema and partial schema coverage, the description covers return values, error reporting, preconditions, and referrals (physics, front_door). Gaps remain around what 'active' means and whether consume destroys the asset, which matters given destructiveHint=false.

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 coverage is only 57% and two parameters (target_id, action) carry no inline description, so the prose must compensate. It does: it states the exact parameter set each action accepts (move: to_place_id + optional carry_thing_id; give: to_handle + thing_id or target_type/target_id), which is conditional logic the schema cannot express. The pairing rule for target_type/target_id merely repeats dependentRequired, and terms like 'active' are not defined.

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 opening names the five concrete actions (move, use, give, consume, go_home) this tool performs, so the verb+resource is clear. It never distinguishes 'act' from siblings that sound adjacent, such as transfer (vs give), home (vs go_home), or thing_edit, leaving an agent to guess which entry point to use.

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?

Per-action guidance exists (which parameters each action accepts, and what move crosses), and there are two explicit routing hints: call physics for pending-effect limits and call browse with view=gazette before working in room #454. However, there is no statement of when to choose act over alternatives like transfer or thing_upgrade, and no exclusions, so usage is only implied.

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