eda_pcb_document_start_canvas_update_calculation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that the calculation includes rendering and property panel updates and warns against misuse, but it does not state side effects, whether the operation is idempotent, what happens if called while already active, or any performance implications.

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 concise, front-loaded with the function signature and return type, followed by a short explanation and warning. It has a minor redundancy with the tool name, but every sentence contributes to the meaning.

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 state-changing operation with no annotations and no output schema, the description is incomplete. It lacks guidance on prerequisites, exact effects, when to use it, and what the boolean return value signifies. The vague warning adds caution but not actionable context.

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 input schema covers 100% of parameters (args array and windowId) with descriptions. The description adds no additional parameter information, so the baseline of 3 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 verb 'start' and resource 'canvas update calculation', with a Chinese translation and a remark explaining that it includes rendering and property panel updates. It distinguishes itself from the sibling 'stop_canvas_update_calculation' and 'get_canvas_update_calculation_status', though it is less differentiated from 'trigger_canvas_update_calculation'.

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 the stop/trigger/get-status siblings. The warning 'if you do not understand the meaning of this switch, do not call this interface' implies caution but does not offer any concrete usage conditions or alternatives.

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