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

Annotations already carry the behavioral profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), and the description adds only the placement detail ('top of the list'). It never explains what the destructive hint means here (e.g., whether unpinning displaces or removes an existing pinned position) or why pinning is considered destructive, leaving the most consequential behavior unexplained.

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 short sentence that front-loads the primary action ('Pins a note to the top of the list'). The trailing 'or unpins it' is largely redundant with the 'pinned' parameter's own schema description, a small amount of wasted text in an otherwise tight definition.

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 two-parameter tool with a rich path schema, full annotations, and no output schema, the description is minimally sufficient. It omits the scope question of what kinds of items can be pinned and the effect of pinning on ordering for folders versus notes, but nothing critical to a correct call is missing.

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 100%, so both 'path' and 'pinned' are fully documented in the schema, which sets the baseline at 3. The description adds nothing beyond the schema and in fact says 'a note' while the path schema explicitly accepts folders, sub-notes, files, and app files, slightly narrowing the apparent scope.

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 states a specific verb and resource ('Pins a note to the top of the list, or unpins it') and captures the toggle nature of the operation, so the agent knows exactly what happens. It does not distinguish this tool from siblings like move or edit, which could also alter list ordering, so it stops short of a 5.

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 paired 'or unpins it' plus the boolean parameter makes the pin/unpin choice inferable, but there is no explicit when-to-use, no statement of prerequisites, and no named alternative (e.g., move) for repositioning content.

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