view_axes

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

The description discloses that the computation is analytical with no projection performed, indicating no side effects. It also describes the return format with an example. Without any annotations, the description adequately conveys the behavior.

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 efficiently structured with a front-loaded purpose sentence, a usage guideline sentence, an example output, and parameter details. Every sentence adds value without redundancy, making it easy to parse quickly.

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 presence of an output schema (not provided but mentioned in context), the description compensates with a JSON example. It covers purpose, usage, parameters, and return format. It lacks error handling details, but overall is sufficiently complete for this computational tool.

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 fully compensates by explaining each parameter: viewport_origin as camera position same as project_to_viewport, viewport_up as up vector with default (0,1,0), and look_at as target point defaulting to origin. This adds essential meaning beyond the schema titles.

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 tool returns the world-to-page axis mapping for a project_to_viewport call, computed analytically without projection. This specific verb+resource combination clearly distinguishes it from siblings like render_view by specifying it is used before rendering to catch axis swaps.

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 explicitly says to use this before rendering a projected view to confirm axis mappings and catches axis swaps before they appear in the render. It provides clear context for usage but does not explicitly state when not to use it or mention alternatives.

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