unity_selection_focus_scene_view

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

The description mentions controlling camera parameters but does not disclose side effects (e.g., whether it modifies selection) or required permissions. Since no annotations are provided, the description carries full burden; it partially fulfills it.

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 sentence listing key capabilities, which is efficient. It could be slightly improved by separating into bullet points or clarifying parameter relationships.

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 has 7 parameters, some nested, the description provides a high-level summary but lacks details on how parameters interact (e.g., does 'position' override framing?). No output schema means return value is not described.

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 100%, so parameters are already documented. The description adds no extra semantics beyond listing actions; for example, it doesn't clarify that 'path' and 'instanceId' are alternatives. Baseline 3 is appropriate.

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 it controls the Scene View camera with specific actions like framing, setting pivot, rotation, zoom, and toggling orthographic. However, it does not explicitly differentiate from sibling tools, though the set of actions is unique among the listed tools.

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 unity_gameobject_set_transform or unity_selection_set. The description lacks context for prerequisites or when not to use it.

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