Hello3DMCP Server

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action ('rotate... downward') but doesn't disclose effects (e.g., how much it moves, if it's reversible, rate limits, or error conditions). For a mutation tool with zero annotation coverage, this is inadequate, though it at least implies a change.

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 core action ('rotate the key light downward') and adds clarifying detail ('in an arc around the center of the model'). There is no wasted verbiage, making it highly concise and well-structured.

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 the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits, usage context, and expected outcomes, leaving significant gaps for an AI agent to operate effectively in this 3D modeling environment.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing confusion or redundancy.

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 ('rotate the key light downward') and the resource ('key light'), specifying it moves 'in an arc around the center of the model'. It distinguishes from siblings like 'swing_key_light_up' by direction, but doesn't explicitly differentiate from other key light tools like 'nudge_key_light_elevation_down' or 'rotate_key_light_counterclockwise', which might have similar effects.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context (e.g., only works if a key light exists), or comparisons to sibling tools like 'nudge_key_light_elevation_down' or 'move_key_light_toward_direction', leaving the agent to infer usage from naming patterns alone.

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