yuque_list_books

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

No annotations are provided, so the description carries the burden. It implies a read operation (listing books), but does not confirm read-only behavior or disclose any side effects. The lack of annotations makes a score of 3 appropriate as it is functional but incomplete.

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 a single sentence with no wasted words, but the ambiguity between 'current user' and the 'login' parameter slightly detracts from its efficiency. It remains mostly concise but could be improved.

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?

Given no output schema, the description does not mention what is returned (e.g., list of book ids or titles). It does not address pagination, filtering, or the scope of 'all books'. For a list operation, more context on the output would improve completeness.

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 schema has 100% coverage describing 'login' as 'User login name', but the description says 'for the current user', creating ambiguity: does it list books of the authenticated user or of the user specified by 'login'? This inconsistency fails to clarify the parameter's role, providing less value than a baseline 3.

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 'List all books' with a specific noun (知识库) and targets the current user, making the purpose understandable. However, it does not explicitly differentiate from sibling 'yuque_get_book' which retrieves a single book, but the name 'list' implies the distinction.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description implies listing all books for a user, but does not mention alternatives like 'yuque_get_book' for specific books, leaving the agent to infer usage from the tool name.

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