get_camera_info

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

No annotations are present, and the description does not disclose whether the operation is read-only, whether it may fail, or any side effects. While the name suggests a getter, this is not explicitly stated, leaving ambiguity about behavioral expectations.

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 extremely concise, using a single line with a parenthetical list of key attributes. It contains no unnecessary words and is easy to parse at a glance.

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 single parameter and no output schema, the description is too brief to provide complete context. It omits crucial information about the parameter's meaning, return format, and potential edge cases, making the tool underspecified for reliable use.

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 parameter 'name' with no description, and the tool description does not explain what 'name' refers to (e.g., camera object name, scene camera, or something else). With 0% schema coverage, the description fails to compensate, leaving the parameter meaning unclear.

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 that the tool retrieves camera details including lens, type, crop, DOF, and active status. The verb 'get' is implied by the title and the resource is specific to cameras, distinguishing it from lighting, object, and other info tools.

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 explicit guidance on when to use this tool versus alternatives. It does not mention scenario constraints, prerequisites, or contrast with sibling tools like get_camera_info vs list_cameras or get_object_info.

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