goodnotes_set_template

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description usefully goes beyond them: it discloses that a PDF backup is saved before the mutation, that picker selection and page identities are verified, and that exported appearance/text are compared across reload. That is real operational context about side effects and safety nets. It still does not say what happens on verification failure or whether the backup is restorable.

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, front-loaded with the action and followed by the behavioral envelope. Every clause carries information; nothing is filler. It could be tightened only slightly, and the verification clause is a bit compressed for how much it implies.

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 destructive, open-world mutation with 6 required parameters, no output schema, and zero schema descriptions, the definition covers side effects well but leaves required-parameter semantics and failure modes undocumented. An agent could not construct a valid call from the description alone — it would still need to guess at operationId and the expected* hash/count values.

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% across 7 parameters, so the description must compensate. It loosely maps to kind (paper/cover), page, and templateId, and 'verifies picker selection and page identities' gestures at expectedPageCount and expectedOrderHash. But url, operationId, and the exact meaning of the two expected* guards are never explained, so the burden is only partly met.

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?

States a specific verb and resource: "Replace a page background or cover with a listed native template." That is far more informative than the name alone and pins down the target (page background/cover, native template) versus a generic style setter. It stops short of differentiating itself from the similarly named goodnotes_set_board_background sibling.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives such as goodnotes_set_board_background or the style tools. The phrase 'listed native template' implies a precondition (the template must be pickable) but never states it as a rule, and required preconditions like the order hash and page count are left unexplained.

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