camera_manage

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

No annotations are provided, so the description fully bears the burden of disclosure. It details effects like 'unmarks previously current cameras' for create with make_current=True, and mentions class-aware behavior and enum-by-name mapping. It could be more explicit about error handling or permissions, but it provides substantial behavioral context beyond basic read/write.

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 clear bullet points for each operation and front-loaded purpose. It is somewhat verbose with minor details like 'Vector2 dict coercion' that are not essential for tool selection, but overall it is efficient and easy to parse for an AI agent.

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 complexity of multiple operations and the presence of an output schema (true), the description covers creation, configuration, limits, damping, follow, inspection, listing, and presets. It notes class-aware behavior and enum mapping. It does not address error scenarios or preconditions for operations like set_limits_2d, but it is largely complete for agent comprehension.

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?

Input schema coverage is 0% because params is a generic object. The description compensates by detailing parameters for each operation, e.g., listing parent_path, name, type, make_current for create, and mentioning Vector2 dict coercion for zoom/offset. It adds significant meaning that the schema lacks, though some property details (like all 'properties' for configure) are not fully enumerated.

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 it is for Camera2D/Camera3D authoring and enumerates all operations (create, configure, set_limits_2d, etc.). It distinguishes itself from sibling tools like node_set_property by specifying that transforms should be set via node_set_property, not here. This provides a specific verb+resource with clear scope.

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 explicit when-to-use guidance, including alternatives (e.g., 'set those via node_set_property, not here') and context for each operation. It does not explicitly state when not to use the tool versus other sibling tools, but the differentiation is clear enough for an AI agent to understand applicable scenarios.

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