geogebra_new_construction

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

The description explicitly states that current objects are cleared, which is a key behavioral trait. Since no annotations are provided, this carries the full burden. However, it does not mention whether unsaved work is lost or if confirmation is required, so it is not fully comprehensive.

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?

Single sentence that is front-loaded with the key action. Every word is necessary and there is no wasted text.

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 parameterless tool with an output schema, the description covers the main behavior (create blank, clear objects). It could mention what happens to the current construction (e.g., unsaved changes), but overall it is adequate.

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?

No parameters exist, so the description naturally adds value by clarifying the tool's effect. Baseline 4 is appropriate as the description provides context beyond the empty 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?

The description clearly states the action: 'Create a new blank GeoGebra construction, clear all current objects.' It uses specific verb+resource and distinguishes from sibling tools like geogebra_create_construction by explicitly mentioning blank start and clearing.

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 implies usage when a fresh start is needed (clear all objects), but it does not explicitly state when to use this tool versus alternatives such as geogebra_create_construction or when not to use it. No exclusions or prerequisites are mentioned.

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