yuque_get_my_repositories

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the basic action without explaining authentication needs, pagination behavior, or effects of parameters like 'include_membered'.

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 communicates the core functionality with no extraneous content. It is appropriately sized for the simplicity of the tool.

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 three parameters and no output schema, the description is incomplete as it does not explain parameter semantics or behavioral details. The tool's convenience is clear, but the lack of guidance on filtering and pagination limits practical usability.

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 description coverage, and the description does not elaborate on any of the three parameters. While the enum values and names are somewhat self-explanatory, 'offset' and 'include_membered' remain ambiguous without additional context.

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 uses the specific verb 'get' and clearly identifies the resources 'current user and repositories', distinguishing it from sibling tools like yuque_list_repos and yuque_get_current_user. The phrase 'in one call' highlights its combined nature, making the purpose unambiguous.

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 for retrieving both user and repositories simultaneously, but it does not explicitly state when to use this tool over alternatives or mention exclusions. The context is clear but there are no direct guidelines for alternate scenarios.

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