yuque_list_repos

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action, omitting details about pagination (offset), filtering (type), the effect of include_membered, or authentication/rate limits. While this is a read-only operation, the lack of behavioral context is a significant gap.

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, front-loaded sentence that efficiently communicates the core purpose. There is no verbose filler or unnecessary information, making it a model of conciseness even though it under-specifies other dimensions.

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 the tool has 5 parameters, no output schema, and no annotations, a one-sentence description is grossly incomplete. It does not explain the meaning of parameters, the types of repos, or the return format. The complexity of the tool is not matched by the description.

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 0% description coverage for its 5 parameters, and the description does not compensate by explaining any of them. Parameter names like 'user' and 'group' are somewhat self-explanatory, but 'include_membered' and the enum for 'type' are ambiguous. The description adds no value beyond the bare bones of the schema.

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 tool's function: 'List repos under a user or group.' It uses a specific verb ('List') and resource ('repos'), and the scope ('under a user or group') distinguishes it from sibling tools like yuque_get_my_repositories and yuque_get_repo.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of specific use cases, exclusions, or comparisons to similar list tools (e.g., yuque_get_my_repositories, yuque_list_docs). The description implies a general listing function but offers no decision-making context.

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