Capture canvas image

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

Annotations indicate readOnlyHint (true) and idempotentHint (false). The description adds that the image is delivered once as its own content block, which is useful behavioral info beyond the annotations.

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, each serving a purpose: first defines the action and rationale, second provides usage guidance and output format. No unnecessary words.

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?

Covers purpose, tab selection, output type (PNG image, content block), and sequencing hint. Given the tool's simplicity and presence of an output schema, the description is fully adequate.

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 sole parameter 'tabId' has no schema description (0% coverage). The description explains that it 'captures the given tab (or last-focused)', adding crucial context that the parameter is optional and defaults to the last-focused tab.

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?

Clearly states it captures the currently visible EasyEDA schematic/PCB canvas as a PNG image for visual verification. Distinguishes itself from sibling 'easyeda_canvas_capture_region' by mentioning that one for framing specific areas.

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 advises using 'easyeda_canvas_capture_region' first to frame a specific area. Clarifies that it captures the given tab or the last-focused one. Provides context for use after draw/place/route actions, though does not explicitly state when not to use.

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