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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior context beyond that: the payload is a JSON envelope containing base64 JPEG data plus metadata, which tells the agent how to parse the result. No auth or rate-limit notes, keeping it short of a 5.

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?

Two sentences, zero filler. The core action and payload are front-loaded, and the alternative-method routing is a tight follow-up sentence.

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?

With no output schema, the description usefully describes the return payload, and the single required param is covered by the schema. Complete enough to invoke correctly; only auth/error behavior is unaddressed, which is minor for a read-only snapshot tool.

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 100% and kernelId is fully documented in the schema, so the description adds no parameter meaning beyond it. Baseline 3 is appropriate; the description's value lies in the return format, not the input.

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?

Specific verb+resource ('Get the latest camera frame from a kernel') plus the exact return shape (JSON snapshot with base64 JPEG + metadata). It also distinguishes this tool from the raw-JPEG path, so an agent can tell what it will receive without opening anything else.

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?

Explicitly states the alternative for the raw JPEG case ('use GET /api/ot2/camera/latest directly'), which is a real routing decision. It lacks any exclusions relative to sibling tools, but the format-choice guidance is clear and actionable.

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