Zoom to Fit

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

With no annotations, the description carries the full burden, but it only states the top-level intent. It discloses no behavioral traits: no mention of whether it animates, modifies the camera across slides, affects selection, or has side effects. This is a significant gap for a tool that alters the viewport.

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, front-loaded sentence that conveys the essential scoping distinction. Every word earns its place, and there is no redundant phrasing or 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?

Despite the low parameter count and lack of output schema, the description omits crucial context: it does not state what 'fit' means visually, which slide/viewport is affected, or whether the fit is immediate or animated. Given that no annotations compensate, the description is incomplete for an agent to confidently invoke 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?

The schema only defines nodeIds as an array of strings with no description. The description adds meaning by implying that providing specific node IDs fits those nodes, while omitting them fits all content. However, it does not explicitly link 'nodeIds' to the parameter or clarify the empty-array behavior, so it partially compensates.

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 action ('zoom to fit') and the two target scopes ('specific nodes or all content'), distinguishing the core function from siblings like set_viewport that manually position the view. It could more explicitly differentiate from that sibling, but the verb+resource+scope is specific enough for a 4.

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 provides no guidance on when to use this tool versus alternatives such as set_viewport or focus_slide. It does not mention exclusions, prerequisites, or that this tool is best for fitting content vs. fine-grained viewport control, so there is no practical usage direction.

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