Stage Grab Rule

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

With no annotations, the description carries the burden and discloses meaningful behavior: grab overrides size/lock, grab=False releases a held hand, fixed holds without moving and releases at 6 cm, clear drops the rule, and the rule is saved in world.json. It does not state precedence when multiple flags are set or any permission/error behavior.

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 and front-loads the core concept before explaining each flag. It wastes little space, though bullet-style structure would improve scanability for the six parameters.

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?

It covers the core behavioral effects and persistence, but with no annotations, 0% schema coverage, and six parameters, it leaves scene/object/scenes and flag interaction rules undocumented. An output schema exists, so return values need not be explained.

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 0% with six parameters, so the description must compensate. It explains grab, fixed, and clear well, but does not define scene, object, or scenes, leaving half the inputs without semantics.

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?

States that it defines one object's grab-by-touch rule and explains what grab, fixed, and clear do. It is clear on the resource and action, but does not clearly distinguish it from the sibling stage_grab_mode, which is only parenthetically named.

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?

No explicit when-to-use or when-not-to-use guidance is given. The parameter effects imply this is for configuring object grab behavior, but there is no routing signal versus stage_grab_mode, stage_object_set, or other stage-object tools.

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