set_camera_speed

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

Despite annotations already declaring the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true), the description adds genuinely non-obvious context: the change affects only this editor session and saves nothing, so the agent knows the effect is transient and non-persistent. It also notes the value can be clamped by the viewport.

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?

Front-loaded with the action and target, followed by the persistence caveat, then the return shape. Slightly redundant: the prose 'Returns requested and camera_speed...' restates the 'Returns: { ... }' line, but the redundancy is minor and the piece stays short.

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?

With no output schema, the description correctly compensates by spelling out the return shape (applied, requested, camera_speed), plus target selection and persistence semantics. Coverage is strong for a simple one-param tool; only explicit error/edge behavior beyond the schema's 0-or-less note is absent.

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%, so the schema already documents 'speed' as a positive float with 0-or-less being an error and the camera_speed comparison hint. The description adds nothing parameter-specific beyond the schema, so the baseline 3 applies.

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 ('Set') and resource ('camera movement speed') on a precisely scoped target: 'the active level editor viewport (the focused one, else the first)'. The focus-else-first disambiguation lets an agent tell it apart from broader viewport/camera setters without opening a schema.

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 (adjust the editor viewport fly speed) but there is no explicit when-to-use guidance, no prerequisites, and no named alternatives among the many viewport/camera siblings such as set_viewport_camera or set_camera_transform. The session-only note helps but is behavioral, not selection guidance.

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