map_rotate

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

Description mentions parameter normalization (0-360) but lacks disclosure of other behavioral traits like whether rotation is persistent, requires confirmation, or affects other elements. Without annotations, this is insufficient.

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?

Single sentence with no filler, front-loaded with the verb. Efficient and to the point.

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?

Adequate for a simple one-parameter tool with an output schema, but lacks usage context and behavioral details. Could benefit from mentioning if rotation is permanent or animated.

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%, but the description explicitly states 'angle in degrees (normalized to 0-360)', adding unit and normalization context beyond the schema.

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 verb 'Rotate' and resource 'map canvas' clearly state the action and target. It distinguishes from sibling tools like zoom and pan by specifying rotation.

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 on when to use this tool versus alternatives like map_zoom_to_layer or map_pan_to. No context about prerequisites or expected use cases.

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