camera_set

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the description only needs to add context beyond that. It usefully notes the default target (active camera) and implies nested/json-or-object attribute payloads, but leaves open whether omitted fields are preserved or reset — a key question for a non-destructive mutation 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?

The key action and default target are front-loaded, and the attribute list plus inline JSON examples add signal without padding. The raw JSON snippets make the sentence less clean to read than prose, but every element is informative, so structure is only slightly penalized.

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?

An output schema exists, so return values need not be described. However, for a nested free-form mutation tool with 0% schema coverage, key gaps remain: ref is undocumented, the full set of settable attributes is only partially enumerated (mode and limits are vague or truncated), and merge-vs-replace semantics for omitted fields are unstated. Adequate but not sufficient for confident invocation.

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%, and the attributes object is free-form with additionalProperties=true, so the description carries the main burden of documenting shape. It does this well for the attributes parameter by naming concrete keys (fov, focalLength, mode) and showing exact nested JSON for lens, postEffect, and limits. It earns a 4 but not a 5 because the ref parameter is never explained.

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 first clause "Set camera attributes (the active camera by default)" names a specific verb and resource and states the default target, so an agent knows it mutates a camera rather than reading it (camera_get) or managing cameras (camera_list, camera_create, camera_set_active). It does not explicitly note when to prefer a sibling such as camera_set_active, keeping it short of a 5.

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 parenthetical "the active camera by default" implies you may target a specific camera via ref, but there is no explicit when-to-use versus camera_set_active, camera_frame, or object_set_transform. Usage is implied rather than spelled out, and no exclusions or prerequisites are given.

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