yuque_create_repo

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the mutation action ('Create') without elaborating on side effects, prerequisites, error conditions, or expected response. The minimal wording adds little beyond the tool's name.

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, concise sentence that avoids redundancy. It is front-loaded and contains no wasted words, making it easy to parse quickly while conveying the core purpose.

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?

With 7 parameters, no output schema, and no annotations, the description is too sparse to provide complete context. It fails to mention required parameters (name, slug), the meaning of 'type' or 'public', or what the tool returns upon success. The description covers only the ownership dimension, leaving significant gaps for an agent selecting and invoking the tool.

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 0%, and the description must compensate. It does clarify the 'user' and 'group' parameters via 'under user or group', which is useful, but it provides no insight into the meaning, format, or purpose of name, slug, type, public, or description. This leaves agents with insufficient semantic context for most parameters.

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 verb 'Create' with the resource 'Yuque repository' and specifies the container as 'under user or group'. It distinguishes this tool from siblings like yuque_update_repo, yuque_delete_repo, and yuque_list_repos by focusing on creation.

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 usage by declaring the creation action, but it does not explicitly state when to use this tool versus alternatives (e.g., yuque_create_doc). The phrase 'under user or group' hints at a choice between user and group ownership, which is a light usage guideline, but no exclusions or comparisons are provided.

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