herdr_pane_zoom

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

Annotations already declare the full behavioral profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds no context beyond them – no note on what zooming visually does, whether it affects other panes, or any resulting state change. The bar is lower with annotations, but this description contributes nothing extra.

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?

A single short sentence with zero waste and the action front-loaded. It is efficient, though arguably terse enough to border on under-specification for a tool with a toggle mode.

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-required-parameter toggle with 100% schema coverage and no output schema, the essentials are covered by the schema. The description is the minimum viable, but adds nothing about behavior or results that would round it out.

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 100%, so both parameters (mode with its enum and default, pane_id with its omission default) are fully documented in the schema. The description adds no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb pair ('Zoom or unzoom') and resource ('a pane'), so the agent knows exactly what operation is performed. It does not distinguish itself from potentially confusable siblings like herdr_pane_resize or herdr_pane_move, but the action is unambiguous.

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 gives no guidance on when to use zoom versus resize or move, nor any prerequisites or exclusions. Usage must be inferred from the name alone.

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