Hello3DMCP Server

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a mutation tool (implied by 'Adjust'), it automatically queries fresh state before adjustment, and it works relative to current position. It doesn't mention permission requirements, rate limits, or error conditions, but provides useful operational context.

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 perfectly concise with two sentences that each earn their place: the first states the core purpose, the second adds crucial behavioral context about automatic state querying. No wasted words, front-loaded with essential information.

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 single-parameter mutation tool with no annotations and no output schema, the description provides good context about the operation's behavior and automatic state management. It could be more complete by mentioning what happens on success/failure or typical response format, but covers the essential operational logic well.

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 description coverage is 100% with the single parameter 'degrees' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline score of 3 for high schema coverage.

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 specific action ('Adjust the key light elevation upward'), identifies the target resource ('key light'), and distinguishes it from sibling tools like 'nudge_key_light_elevation_down' and 'set_key_light_position_spherical' by specifying it's a relative upward adjustment from current position.

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 provides clear context about when to use this tool: for upward adjustments relative to current position, with automatic state querying for accuracy. However, it doesn't explicitly state when NOT to use it or name specific alternatives like 'set_key_light_position_spherical' for absolute positioning.

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