list_subscribe_topics

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape (topics[], has_more, total) and a non-obvious edge rule ('cannot treat an empty library as no notes'). However, it never states read-only semantics explicitly, nor how results combine with or differ from the user's own library, leaving gaps for a tool with zero annotation coverage.

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?

Every clause carries information, but the description is a single dense run-on that interleaves purpose, scope defaults, and multi-step fallback routing. It is hard to parse quickly and the routing logic is not ordered for front-loading the core action.

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?

No output schema exists, but the description names the returned fields (topics[], has_more, total). All six params are schema-documented at 100% coverage, and the fallback behavior is explained. An agent has enough to call it correctly, though the empty-result handling could be clearer.

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 the schema already documents page, query, scope, author, book_id and page_size with defaults and enums. The description reinforces the DEFAULT vs BOOKSPACE split and the query/author/book_id/pagination handling but adds little beyond what the schema states.

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 opening states a specific resource and scope: knowledge bases the current user actually subscribes to, explicitly excluding self-created ones. This distinguishes it from the sibling list_topics (own libraries) without naming it outright. An agent can tell what it returns, though the counterpart tool is only implied.

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 concrete routing: 'when own library has no match, supplement here,' and further prescribes a fallback to list_notes' personal-reference route with a condition ('user hasn't limited to only subscribed libraries'). It covers when-to-use and alternatives. The guidance is somewhat buried in dense prose rather than cleanly front-loaded.

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