goodnotes_board_settings

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds no behavioral context beyond that — nothing about whether the board must be currently open, whether the URL must resolve to an existing board, or what happens on an unreachable URL. With annotations carrying the safety burden, this is a neutral 3 rather than a failure.

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?

A single front-loaded sentence with no filler or repetition; every word specifies the resource being read. Nothing is wasted, though there is very little text overall.

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 one-parameter read-only tool with no output schema, the description does hint at the returned fields (pattern and color), which partly compensates for the missing output schema. However, the sole required parameter is left entirely unexplained at 0% schema coverage, which is a real gap for correct invocation.

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 explains what that URL identifies — a board, a document, a share link, or an open session — nor any accepted format. It mentions 'whiteboard' generically but contributes no meaning an agent could use to construct a valid URL.

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 description gives a specific verb ('Read') and a specific resource ('whiteboard background pattern and color'), so an agent knows exactly what is fetched. It implicitly contrasts with the sibling goodnotes_set_board_background through the read/write split, but never names that alternative to make the distinction explicit.

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: an agent can infer this is the inspection counterpart to goodnotes_set_board_background, but the description never states when to call it, what prerequisite state is needed, or that any alternative exists for changing the values.

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