tracking.solve_camera

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

Annotations are all false (no hints), so the description must carry the behavioral disclosure burden. It does not describe side effects, scene modifications, idempotency, or what happens when camera solving is performed. The phrases 'Risk: standard' and 'maturity: L3' are generic metadata, not revealing any concrete 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 extremely brief, but brevity here is under-specification rather than conciseness. It fails to include essential purpose and usage information, and the one sentence is mostly occupied by generic risk and policy statements rather than actionable tool-specific content.

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?

There is no explanation of what the tool does, no parameter details, and no mention of the output schema or expected return values. An agent has no basis to correctly call this tool or interpret its result. Even with an output schema present, the total lack of semantic context makes the definition incomplete for any meaningful 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?

Schema coverage is only 43%; the core functional parameters (clip, keyframeA, keyframeB) have no schema descriptions. The tool description adds zero parameter semantics, failing to explain what these parameters mean or how they relate to camera solving. No compensation exists for the low schema coverage.

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 repeats the command name 'tracking.solve_camera' and labels it a 'PartMe Blender Harness command'. It does not state what the tool actually does (e.g., solving camera motion from tracked features). This is a tautology that restates the title, so it scores 2.

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 given on when to use this tool versus its siblings such as blender_tracking_add_track or blender_tracking_setup_scene. The only note about 'per-request argument checks and session policy' is generic and applies to all harness commands, so it provides no situational or alternate-tool guidance.

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