camera.create

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

The annotations already signal that this is not read-only or idempotent, and the description adds only generic notes about risk and maturity. It does not disclose actual invocation effects such as whether a camera object is created, whether duplicated names are allowed, what state changes occur, or how transactions interact with the creation.

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 short, but its words are mostly redundant or generic; 'camera.create' repeats the title, and risk/maturity phrasing could apply to any harness tool. It is under-specified rather than usefully concise, so it does not earn its place.

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?

Despite an output schema and annotations, this tool has 9 parameters, is mutating, and belongs to a large family of camera/Blender tools; the description is far too thin for an agent to invoke it confidently. An agent would still need to infer the essential behavior and required context from the name and schema alone.

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 prose adds no parameter-level meaning beyond the input schema. With only 56% schema description coverage, several fields like 'lens', 'active', and '_expectedSceneRevision' still have no semantic explanation, and the tool description does nothing to bridge that gap.

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 only says 'PartMe Blender Harness command `camera.create`', which repeats the tool/title rather than explaining that this command creates a Blender camera. It does not clarify how this differs from siblings such as blender_camera_add_handheld or blender_camera_follow_path.

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?

There is no when-to-use or when-not-to-use guidance. The only contextual statement is that per-request argument checks and session policy apply, which is broad policy boilerplate rather than guidance for choosing this tool over its siblings.

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