read_camera

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'read', which implies a non-destructive operation, but it does not explain what happens if the camera is not found, what specifically constitutes 'configuration', or whether the return value is a summary or full detail. Compared to similar read tools, this lacks sufficient behavioral context.

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 concise sentence, front-loaded with the core action. It is appropriately short for a simple read tool, though it could benefit from a brief note about the scene file dependency. No wasted words, but the terseness contributes to its incompleteness.

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?

With only 2 parameters (one required), no output schema, and no annotations, the description should provide more context but does not. It fails to mention that the tool operates on a specific scene file, what camera configuration details are returned, or how the optional 'camera_name' parameter behaves. The schema covers parameter syntax, but the description leaves important usage context unexplained.

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% (both parameters have descriptions), so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides, but it doesn't need to since the schema is complete. No contradiction or missing parameter information.

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 says 'Read camera configuration', which clearly identifies the verb ('read') and resource ('camera configuration'). It is more specific than just 'read camera', but it does not distinguish itself from sibling tools like 'read_scene' or 'editor_get_camera' that also deal with camera-related 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 provides no guidance on when to use this tool vs alternatives. There are many sibling tools (e.g., 'list_cameras', 'read_viewport', 'editor_get_camera') but no mention of preferred use cases, prerequisites, or exclusions. The schema indicates it takes a scene path and optional camera name, but the description does not contextualize this.

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