yuque_get_user_repos

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

No annotations provided. The description only mentions a read permission requirement. It does not disclose behavioral traits such as pagination behavior, error handling, or response format. For a read operation, minimal transparency is provided.

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?

Description is concise with a clear header and list of parameters. No unnecessary words. Could be slightly improved by grouping or formatting, but overall efficient.

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?

While it covers parameters well and has an output schema (not shown), the description lacks details on pagination defaults, error conditions, or response structure. Adequate for a straightforward list tool but missing some context.

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 0%, but the description adds meaningful information for each parameter: login (用户 login), offset (偏移量), limit (每页数量), type (知识库类型, with examples Book/Design/System). This adds value beyond the schema's basic type and title.

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?

Clearly states '获取指定用户的知识库列表' (get repository list for a specified user). Distinguishes from sibling tools like `yuque_get_repo` (single repo) and `yuque_get_group_repos` (group repos) by specifying 'user 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?

Explicitly mentions permission requirement ('read') and lists parameters. However, no guidance on when to use this tool versus alternatives, or exclusions. The distinction from sibling tools is implied by the description but not stated.

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