frame_all

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately conveys that the tool changes the viewport view to encompass all objects, and 'Frame' implies a view-only camera adjustment rather than a destructive operation. It does not spell out side effects, but for a zero-parameter viewport command the description is adequately transparent.

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 concise sentence that states the action, target, and scope with no filler. It is front-loaded with the verb and resource, making it immediately scannable. Every word earns its place.

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 simple zero-parameter viewport command, the description is complete: it states the action, the object of the action, and the intended result. The presence of an output schema means return values do not need explanation. Mentioning frame_selected as an alternative would be a minor enhancement, but nothing essential is missing.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter-specific meaning, but none is needed since the input schema is empty. The action and scope are fully described without any parameter ambiguity.

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 uses a specific verb ('Frame') with a clear resource ('viewport') and scope ('all objects'). It clearly distinguishes this tool from the sibling frame_selected, which would frame only selected objects. The parenthetical '(Home key)' adds a useful familiar reference.

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 clearly implies the usage context: use this when you want the viewport to display all objects. It does not explicitly mention alternatives like frame_selected, but the phrase 'all objects' makes the intended condition clear. No exclusions or when-not guidance are provided, so it falls just short of a 5.

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