reset

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

No annotations are provided, so the description must disclose all behavioral traits. It indicates that the view can be reset and optionally an object's matrix, but does not specify what 'reset' means (e.g., default camera position, transformation identity matrix), side effects, or any permissions required. This is minimally transparent.

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, concise sentence that is to the point and front-loaded. It earns its place with essential information, though combining the two actions could be slightly clearer.

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?

Given the context of one optional parameter and a declared output schema (not shown in description), the description is incomplete. It does not explain return values (despite output schema existing), nor does it help the agent choose among numerous sibling tools. More detail on reset behavior and output would improve completeness.

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?

With 0% schema description coverage, the description adds meaning by explaining that the 'obj' parameter optionally resets that object's matrix. This clarifies the parameter's role beyond the schema, which only lists it as optional string/null. However, it does not elaborate on the format or expected values.

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 states the verb 'Resets' and the resource 'view' or 'object's matrix', clearly indicating the tool's action. It is specific enough to differentiate from general tools like 'refresh' or 'rebuild', though it could be more explicit about distinguishing from 'orient'.

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. It does not mention prerequisites, when not to use, or any context that helps the agent decide between reset and other view-related tools like orient or center.

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