center_camera_on_selection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently explains that centring moves the camera without re-framing, potentially dropping parts of the model outside the image, and that session_id is required because camera position is scene state. It also details the behavior of move_vantage, including the default and its effect.

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 well-structured with a clear main line, usage context, and an Args section. Every sentence contributes: it explains the rationale, prerequisites, side effects, and parameters without filler. The length is justified by the behavioral nuances it conveys.

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 no annotations and a simple output schema, the description fully covers what an agent needs: purpose, preconditions, side effects, parameter details, and a note about the return confirmation. It addresses all context needed for correct tool invocation.

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?

Despite 0% schema description coverage, the description's Args section adds substantial meaning beyond the schema. It explains why session_id is required (scene state would be discarded) and clarifies the semantics of move_vantage (True centres most precisely, False re-aims from current position). This goes far beyond the bare schema definitions.

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 opens with a specific verb and object: 'Point the camera at the current selection set.' This clearly identifies the tool's purpose and its unique role among siblings. It further clarifies by explaining why centring helps small selections, especially edges, distinguishing it from other camera or selection 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?

The description explicitly states prerequisites ('Set the selection first with select_entities'), provides a follow-up action ('Follow with snapshot passing zoom=False'), and explains why zoom=True would undo the centring. This gives clear when-to-use and when-not-to-use guidance, fully differentiating it from alternatives.

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