get_camera_overlay_metadata

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

With no annotations, the description carries the burden well by disclosing the required capability, platform limitation, no-image-transfer behavior, and the 404 condition. It does not explicitly state read-only semantics or describe the exact response structure, but the behavior is largely clear.

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 very concise and every clause adds useful information. It is slightly telegraphic and leads with a prerequisite rather than the core purpose, but it remains efficient.

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 there is no output schema and no parameters, the description provides enough context to call the tool correctly: capability, platform scope, no image transfer, and error condition. It could be more complete by naming the returned fields' structure or explicitly contrasting with get_camera_overlay.

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 tool has zero parameters, so there is no parameter semantics to explain. The baseline score for a no-parameter tool applies.

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 the resource and returned metadata: camera overlay size, workspace placement in mm, and revision token. The phrase "without transferring the image" distinguishes it from the sibling get_camera_overlay tool.

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?

It gives useful usage context: requires the "project" capability, is LightBurn-only, and returns 404 when no overlay is loaded. It implies when to use it instead of fetching the image, but does not explicitly name the sibling alternative.

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