goodnotes_render_page

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds the per-page granularity and the desktop-capture exclusion. It does not disclose what the render returns (image bytes, URL, or inline content), whether repeated calls are cached, or how maxDimension affects output.

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 short sentences, front-loaded with the verb and resource, with no filler. The trailing "No desktop capture" is terse to the point of being cryptic, but it earns its place as a scoping exclusion.

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 and 0% parameter documentation, the description should explain what a rendered page looks like and what the size control does; it does neither. For a tool whose whole value is the returned page artifact, this leaves the agent guessing at the output contract.

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% for all three parameters, so the description carries the full burden and mostly fails: only "one ... page" hints at the page index. exportId is never explained as requiring a prior export, and maxDimension (default 1600, range 500-2400) is left entirely undefined as to units or trade-off with legibility.

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?

"Render one exported PDF page" states a specific verb and resource, and the following clause names the concrete payloads it serves (handwriting, scans, diagrams, layout). It does not name a sibling or state how it differs from export/capture tools, so it falls short of the top band.

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?

Usage is only implied: the word "exported" signals an export must exist first, and "No desktop capture" excludes one class of use, but no alternative tool is named. An agent must infer from the sibling list whether this or goodnotes_export / goodnotes_inspect is the right call.

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