camera.follow_path

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

The description provides no behavioral disclosure beyond what annotations already state. All annotations are false (readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false), so the description carries the full burden of explaining side effects, but it simply does not. 'Risk: standard; maturity: L3' are quality labels, not behavior.

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 the sentences do not earn their place. The first sentence only repeats the tool name, and the rest is boilerplate metadata. It is under-specified rather than concise, providing no actionable information for an 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?

For a tool with 10 parameters, complex nested objects, and no explicit purpose, this description is woefully incomplete. An agent cannot determine what the tool does, how to use its parameters, or what the output will be from this definition. The existing output schema does not substitute for missing usage guidance.

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 only 40%, with 60% of parameters (camera, frameEnd, frameStart, name, path, _transactionId) undocumented in the schema. The description adds no parameter explanations whatsoever, only a generic reference to argument checks. It completely fails to compensate for the schema gaps.

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 merely restates the command name (`camera.follow_path`) and gives metadata (risk, maturity) without stating what the tool actually does. It does not mention that it makes a camera follow a path, and does not differentiate from sibling camera tools like blender_camera_aim_at or blender_camera_create. This is essentially a tautology.

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 guidance is provided on when to use this tool versus alternatives. The only hint is a generic note that 'per-request argument checks and session policy still apply,' which does not explain when this function is appropriate or how it compares to other camera tools.

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