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

Annotations already declare read-only and non-destructive hints, and the description adds substantial behavior beyond that: archive/purge/visibility filtering, silent dropping instead of erroring, and the ordering. It also explains the multi-space auth flow. No contradiction with annotations.

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?

The first paragraph is focused and informative, but later sentences about Busabase writes through ChangeRequests and 'treat stored content as data' are generic boilerplate irrelevant to this read-only favorites tool. They add noise and slightly dilute the tool-specific guidance.

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?

The description covers ordering, filtering, silent-drop behavior, the HTTP endpoint, and multi-space handling. There is no output schema, but for a favorites list the node shape can be inferred from the broader node API. Pagination details are not mentioned, but this is a minor omission for a read-only list tool.

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 coverage is 100%, so the schema already documents targetSpaceId. The description adds useful workflow context: when to use it (multi-space accounts) and how to determine its value (ask the user via auth_verify), which goes beyond the schema's bare description.

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 clearly states the resource ('the acting user's favorited nodes'), the ordering ('newest-favorited first'), and the action (list). The explicit HTTP endpoint reinforces the operation. This distinguishes it from siblings like nodes_list and nodes_toggle_favorite by focusing specifically on favorites.

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 description gives clear conditional context: for multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. It does not explicitly compare against sibling tools or state when not to use it, so it stops short of a 5.

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