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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description does not contradict them. It adds behavioral context with 'orbital' and 'ENU transform', but does not disclose whether the camera animates or jumps, or any side effects. With annotations present, this is adequate but not rich.

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, compact sentence with no filler. It front-loads the core purpose and includes relevant technical context (ENU, heading/pitch/range). It is appropriately concise, though it could arguably be more structured.

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 moderate-complexity tool with 6 parameters and no output schema, the description relies on the schema and annotations for completeness. It covers the basic purpose but lacks usage guidance, behavioral details, and distinction from sibling camera tools. It is minimally viable but not fully complete.

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 description coverage is 100%, so the schema already documents all six parameters with Chinese descriptions. The description mentions heading/pitch/range and ENU transform, but does not add meaning beyond what the schema provides, meeting the baseline of 3.

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 tool's function: an orbital camera looks at a given position (环绕式相机注视某位置), with specific details on ENU transformation and control over heading/pitch/range. While it doesn't explicitly name sibling tools, the 'orbital' aspect distinguishes it from generic view/flyTo tools, earning a 4.

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—make the camera orbit/look at a target—but gives no explicit guidance on when to choose this over alternatives like flyTo, setView, or startOrbit. There are no exclusions or alternative mentions, so it only meets the 'implied usage' level.

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