goodnotes_list

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the return values are itemPath strings usable for opening documents — but says nothing about pagination, whether subfolders are included, or what happens with a deep folderPath.

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 action and followed by the most useful return-value fact. Nothing is redundant; the brevity is appropriate, though the first sentence's ambiguity costs it a point.

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 three undocumented parameters including a non-obvious UUID path array, no output schema, and unknown recursion behavior, the definition leaves too much for the agent to guess. A one-line explanation of folderPath and pagination would have closed the gap.

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?

All three parameters have 0% schema description coverage, so the description carries the full burden and provides none of it. It never explains that folderPath is an ordered array of up to 12 UUIDs forming a path, nor what limit/offset do or that the default limit is 30.

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?

"List one library folder. Returns itemPath values for opening documents." does state a verb and resource, but "list one library folder" is ambiguous — it could mean listing folders in a library or listing the contents of a single folder. The second sentence hints the latter (items with itemPath for documents), yet the agent must infer it, and nothing distinguishes it from siblings like goodnotes_list_pages or goodnotes_list_trash.

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 when-to-use guidance is given beyond the implicit "you want a listing." There is no mention of prerequisites, no exclusion of the other list_* siblings, and no note about when to recurse versus call again.

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