yuque_get_book_stacks

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the authentication requirement and the GET read-only endpoint, but it omits pagination behavior, rate limits, error handling, and whether all stacks are returned by default.

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 description is compact and front-loaded: it states the resource, scope, authentication prerequisite, and endpoint in sequence without filler. Every clause contributes useful information.

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 simple parameterless read tool, the description covers the core purpose, scope, authentication requirement, and endpoint. It could be slightly more complete by mentioning pagination or return structure, but no output schema exists that would otherwise carry that burden.

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?

The input schema has zero parameters, so there are no parameter semantics for the description to add. The baseline for a parameterless tool is 4.

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 (当前用户的知识库分组/书架列表), and clarifies the scope includes each stack's knowledge bases. It is clearly distinguishable from sibling mutation tools like yuque_update_book_stack and yuque_sort_book_stack as well as generic list_repos.

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 implies the tool is a read/list operation and gives the required authentication (cookie+ctoken), but it does not explicitly say when to use this tool versus alternatives such as yuque_get_user_groups or yuque_list_repos. Usage context is therefore only implied.

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