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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/non-destructive profile is covered. The description adds the valuable field-to-object-type mapping, but says nothing about whether omitted fields are left untouched, whether edits are reversible, permission requirements, or failure modes for mismatched object/field combinations.

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?

It is a single dense sentence with no wasted filler, which is good, but the nesting ('a canvas's, label's or door's look') makes it hard to parse on first read and buries the primary action behind the odd phrase 'changes something placed'.

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 an 8-parameter mutation tool with no output schema and partial schema coverage, the description covers most editable fields but omits partial-update semantics, error behavior, and what the response contains. Adequate to attempt a call, not complete enough to call confidently.

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 38% (only id, name and keep_for are documented), so the description must compensate — and it largely does, explaining text, picture, look, destination/arrive_at, keep_for and name. The remaining weakness is that the destination vs arrive_at distinction and the exact per-object-type applicability of each field stay fuzzy.

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 names a specific mutation (editing existing placed objects) and enumerates exactly which attributes of which object types can change — label text, door plate, canvas picture, look, door destination, zone keep_for/name. It implicitly separates itself from add_object/remove_object/move_object by being the attribute-editing operation, though the phrase 'something placed' is vague and the object taxonomy is idiosyncratic.

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?

There is no guidance on when to use this versus change_appearance, appearance, move_object, or change_room_settings, all of which plausibly overlap. It never states prerequisites (e.g. that the id must come from look) or what happens if a field is inapplicable to the object type.

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