Hello3DMCP Server

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

No annotations are provided, so the description carries full burden. It describes the action but lacks behavioral details like whether this is a relative or absolute movement, the step size, if it requires specific permissions, or what happens at boundaries. 'Move' implies mutation but safety aspects are undocumented.

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 a single, efficient sentence that front-loads the key action ('Move the fill light') and provides all necessary context without redundancy. Every word earns its place.

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?

Given 0 parameters and no output schema, the description is complete for a simple mutation tool. However, without annotations, it lacks details on behavioral traits like step size or safety, which is a gap for a tool that likely modifies state.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics (none exist), but this is appropriate. Baseline is 4 for 0 parameters as per rules.

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 clearly states the action ('Move'), the target ('fill light'), the direction ('farther from the center'), and the reference frame ('along the axis from the model origin'). It distinguishes from sibling tools like 'walk_fill_light_in' by specifying outward movement.

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?

The description implies usage when moving the fill light outward, but doesn't explicitly state when to use this versus alternatives like 'set_fill_light_distance' or 'move_fill_light_toward_direction'. However, the context of sibling tools suggests it's for incremental outward movement.

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