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

With no annotations, the description carries the full burden. It usefully discloses that threeD selects a HyperRealistic 3D model and that borderless frames are excluded, which is genuine behavioral context, but says nothing about permissions, reversibility, or side effects on existing frames/screenshots.

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?

Three tightly written sentences with the core action front-loaded and no filler. The trailing restriction sentence is worth its space, though the phantom rotation parameters add noise.

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 no-annotation mutation tool with an output-less schema and two undocumented parameters, the description covers only the threeD axis. It omits the semantics of enabled/platformSetId and any safety or return-behavior context, and introduces parameters that aren't callable.

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 33% (only threeD is documented), so the description should compensate for enabled and platformSetId, which it does not. Worse, it references rotationX, rotationY, and rotationZ parameters that do not exist in the schema, which can mislead an agent about the call shape.

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 a specific verb (enable/disable) and resource (realistic device frame on a platform set), which is enough to separate it from frame-adjacent siblings like set_squircle_frame and set_show_notch. It stops short of naming those alternatives explicitly, so it earns a 4 rather than 5.

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?

Usage is implied by the enabling/disabling framing and one real constraint is given ('3D works on every device except borderless-frame and android-borderless-frame'). However there is no guidance on when to pick this over set_squircle_frame/set_show_notch or what state the platform set must be in.

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