goodnotes_list_pages

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses two real behaviors: it refuses to operate on incomplete or virtualized sidebars, and it invalidates canvas handles as a side effect. Those are non-obvious traits an agent must know before calling, though the invalidation side effect is not explained in terms of its consequences.

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?

Three short fragments keep it compact and front-loaded, with no wasted padding. However, the compression goes too far: 'count and order fingerprint' and 'Invalidates canvas handles' read as internal shorthand rather than agent-readable statements.

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, the description does at least hint at the returned data (page identities, count, order) and names the refusal condition, which covers the essentials for a single-parameter read tool. It is still incomplete on the meaning of url, the returned structure, and what invalidating canvas handles means for subsequent calls.

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?

There is one required parameter, url, with 0% schema description coverage, and the description never mentions it. It is unclear whether url refers to a document, a notebook, or a page, or what form is expected beyond the uri format, so the description fails to compensate for the coverage gap.

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 verb 'Read' plus the resource phrase 'native page identities, count and order fingerprint' gestures at listing page metadata, but the phrasing is telegraphic and 'order fingerprint' is undefined. An agent can guess this enumerates pages, yet cannot confidently distinguish it from siblings such as goodnotes_list or goodnotes_manage_pages based on the text alone.

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 only guidance is the constraint 'Refuses incomplete/virtualized sidebars', which describes a failure precondition rather than when to choose this tool. There is no statement of when to use it instead of goodnotes_list or goodnotes_manage_pages, and no mention of what a complete sidebar looks like.

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