frame_selected

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

No annotations are provided, so the description carries the full burden. It clearly states the viewport will be re-framed to show selected objects and adds the shortcut, which is sufficient for a non-destructive viewport command. It does not cover edge cases like empty selection, but those are low-risk for this operation.

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 entire description is a single nine-word sentence with a parenthetical shortcut. It is front-loaded with the key action and contains no filler.

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 zero parameters, no annotations, and an existing output schema, the description covers the meaningful input state and the effect. The only minor gap is not stating behavior when nothing is selected, but this is a minor edge case for a viewport framing command.

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 and the schema is empty, so there is no parameter meaning to explain. The description's 'selected objects' actually communicates the implicit state the command depends on, which adds value beyond the schema baseline.

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 names a specific action ('Frame the viewport') and target ('selected objects'), and includes the Blender shortcut 'Numpad .'. It clearly distinguishes from the sibling frame_all by specifying the selected-object scope.

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 phrase 'selected objects' gives clear contextual guidance for when to use the tool, and the sibling list makes frame_all the obvious alternative for framing everything. It does not explicitly name that alternative, so it stops short of full exclusion guidance.

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