scope_math_zoom_info

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

Description indicates it is a read operation (no side effects), provides parameter range (1–4), and includes VBS transport details. No annotations exist, so description adds useful behavioral context.

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?

Two sentences plus parameter and transport info, no fluff, front-loaded with purpose.

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?

Covers all necessary aspects for a simple read tool with one parameter and an output schema. Could mention output format but not required.

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 has 0% coverage; description adds meaning by specifying 'Math function number 1–4' for the `func` parameter, beyond the type-only schema.

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?

Explicitly states 'Read the current horizontal zoom settings for a math trace' with specific verb and resource, clearly distinguishing it from sibling `scope_set_math_zoom`.

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?

Implied usage as a read operation for zoom settings, but no explicit guidance on when to use vs alternatives like `scope_set_math_zoom` or `scope_math_info`.

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