get_current_viewer_state

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

No annotations provided, so description carries full burden. It describes the output (camera, selections, models) and requisite (extension open). It implies a read-only operation and warns about staleness, but doesn't explicitly state side effects or authentication needs. Overall transparent enough for a read tool.

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?

Very concise: three sentences that flow logically from purpose to prerequisite to usage advice. No wasted words, front-loaded with key information.

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 no output schema, the description thoroughly describes what is returned and includes actionable guidance (extension requirement, staleness check). Covers all necessary context for the agent to use the tool correctly.

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; schema coverage is 100% (empty). Description correctly adds no unnecessary parameter info. Baseline 4 applies as there is nothing to explain.

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 retrieves the live state of the user's 3D viewer, listing specific components (camera, selected objects, models, snapshot). It explicitly says when to use it (requests about what user currently sees), distinguishing it from sibling tools like get_current_user or tc_list_views.

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?

Provides clear context: use when referring to current view, requires 'Agent Eyes' extension to be open, and advises checking age_seconds/stale. However, no explicit alternatives or when-not-to-use guidance given, but the usage advice is sufficiently directive.

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