camera.report

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions defaulting behavior but does not state that the tool is read-only, what information is reported, or any side effects. For a report tool, the lack of explicit read-only indication is a gap.

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 of 10 words, efficiently conveying core purpose. However, it omits important details like output or read-only nature, which could be added without becoming verbose.

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 has one parameter, no output schema, and no annotations, the description is insufficient. It does not describe what the report contains (e.g., properties, transforms), error behavior, or confirm it is a read operation. For a simple query tool, this leaves significant gaps.

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?

The schema has one optional string parameter 'Camera object name' with a default of empty string, but no schema descriptions. The description adds meaning by explaining that an empty value defaults to the active scene camera. However, it does not clarify what format the camera object name should be (name, ID, etc.), leaving ambiguity.

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?

Description clearly states verb 'Report' and resource 'one camera', with scope 'defaulting to the active scene camera'. It distinguishes from sibling tools like camera.list (which lists all cameras) by focusing on a single camera. However, it does not differentiate from other report tools (e.g., light.report, world.report) beyond the resource name.

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?

No explicit guidance on when to use this tool versus alternatives like camera.set or camera.list. The phrase 'defaulting to the active scene camera' implies a use case for retrieving info about the active camera, but no when-not or comparison with siblings is provided.

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