goodnotes_convert_handwriting

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

Annotations already flag destructive writes; the description adds real context beyond them, namely that the document must be writable, that existing handwriting is replaced, and that the resulting text is verified after a reload. It still omits what happens to the original strokes on failure and whether the operation is idempotent.

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 tight sentences with the destructive action front-loaded and the optional correction and verification follow-ups trailing. Dense but readable; the verification clause is somewhat compressed, but nothing is wasted.

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 three-parameter destructive tool with no output schema, the definition covers the core action and one post-condition but leaves the return value, failure behavior, and the meaning of operationId unaddressed. Adequate, but an agent would still have to guess at the required identifiers and the result shape.

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 description coverage is 0%, so the description carries the full burden, yet it explains only the optional text parameter (as a correction override). handwritingId and especially operationId, which is constrained by a pattern but never described, are left for the agent to infer.

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?

Names a specific verb and transformation: replacing already-recognized handwriting with editable text in a writable document. This clearly separates it from a read-only sibling such as goodnotes_read_handwriting, but it never names an alternative explicitly, so the differentiation is implied rather than stated.

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?

The phrase "previously recognized handwriting" and "optionally correct recognition text first" imply the precondition that recognition must already have happened and hint that the caller can pass corrected text. There is no explicit when-to-use/when-not or named alternative, and no statement about what to do if the handwriting was never recognized.

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