reset_view

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

With no annotations, the description must fully disclose behavior, but it only states the action without detailing side effects, required state (e.g., molecule must be loaded), or whether the reset is instantaneous or animated. The absence of any behavioral context beyond the purpose is a significant gap.

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 very brief (one sentence) but lacks structure. It does not front-load critical information or separate purpose from usage. While concise, it sacrifices clarity by omitting parameter details.

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 one optional parameter and no output schema or annotations, the description is insufficient. It does not specify what 'reset/fit' means in terms of camera behavior, whether it applies to all loaded molecules, or if there are any side effects. The description feels incomplete for an agent to reliably use the tool.

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 description coverage is 0% (the parameter 'molid' has no description in the schema), and the tool description does not explain the parameter's role, such as selecting which molecule's view to reset. This leaves the agent with no information to correctly set the parameter.

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 'reset/fit' and the resource 'camera to the loaded molecule', effectively communicating the tool's function. It distinguishes from siblings like zoom_view and rotate_view by implying a return to a default fitting view, though it could specify which molecule if multiple are loaded.

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 such as zoom_view or rotate_view. There is no mention of prerequisites (e.g., needing a loaded molecule) or scenarios where resetting the view is appropriate.

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