get_view

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

No annotations are provided, so the description carries full burden. It states 'Get a screenshot' implying a read-only operation with no destructive side effects, but it does not disclose any performance implications, authorization requirements, or error handling 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 well-structured with clearly labeled sections for Args and Returns, but it includes some repetitive wording (e.g., 'The following views are available:' could be more concise). Overall, it is clear and front-loaded.

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 tool's simplicity (screenshot capture) and the presence of an output schema, the description is sufficiently complete. It covers all parameters, their defaults, and the return type, though it could mention expected output format or dimensions.

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 0%, so the description must add meaning. It explains view_name with all enum values, width and height defaults, and focus_object purpose. This adds substantial value beyond the bare 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 'Get a screenshot of the active view', specifying the verb (Get) and resource (screenshot of view). It also enumerates all available views, distinguishing it from sibling tools like get_object or get_objects which retrieve object data.

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 explains how to use the tool by listing parameters and options, but it does not explicitly state when to use this tool versus alternatives (e.g., using get_object for individual object details). No exclusion criteria or when-not-to-use guidance is provided.

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