viewport_focus_object

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It mentions 'zoom to fit' but does not explain how the viewport is adjusted (e.g., does it change camera type? does it affect locked views?), nor does it address potential side effects or required permissions. The behavioral description is insufficient for an agent to predict the tool's impact.

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 extremely concise—two short sentences—and front-loads the essential purpose. Every word contributes meaning without redundancy. It efficiently communicates the core action.

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 simplicity (one required parameter, no output schema, no annotations), the description is minimally adequate but lacks details about error handling, behavior when the object name is ambiguous, or what 'focus' entails exactly (e.g., does it change the active view? does it respect locked cameras?). A more complete description would address these edge cases.

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 schema description coverage is 0%, so the description must compensate. It provides 'Object to focus on' for the only parameter, which adds minimal meaning beyond the property title 'Object Name'. It does not specify format, uniqueness constraints, or behavior if the object is not found.

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 verb 'focus' on the resource 'viewport' for a specific object, with the parenthetical 'zoom to fit' clarifying the behavior. This is distinct from other viewport tools like viewport_set_view which manipulate camera position generally, or viewport_set_shading which changes appearance.

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. There is no mention of prerequisites, typical use cases, or conditions under which another tool might be more appropriate. The description only states the action without context.

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