geogebra_set_view

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

No annotations are present, and the description does not disclose non-obvious behaviors (e.g., whether view changes are permanent, require authentication, or affect existing objects). Only parameter values are explained.

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 extremely concise: one sentence for the action and one line for parameter semantics. Front-loaded with the action, no redundant content.

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 single-parameter tool with an output schema (which likely covers return values), the description is largely complete. It lacks minor contextual details like persistence or app scope, but suffices for basic usage.

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 provides no enum or description for the parameter (0% coverage), but the description lists all valid values with their meanings (e.g., 'G'=几何). This fully compensates for the schema gap and enables correct tool invocation.

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 explicitly states the action ('设置 GeoGebra 视图模式' - Set GeoGebra view mode) and the parameter purpose. It clearly distinguishes from sibling tools like geogebra_set_appearance, but does not elaborate on the scope of the view change.

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 geogebra_set_appearance or geogebra_create_construction. The description lacks context for proper selection.

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