yuque_get_current_user

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Get current Yuque user profile,' which implies a read operation, but it does not disclose authentication requirements, potential errors, rate limits, or any side effects. For a tool with zero annotation coverage, this is minimal transparency.

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 one concise sentence that directly conveys the tool's purpose with no redundant or extraneous text. It is appropriately sized for its simplicity.

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's very low complexity (no params, no output schema, simple read operation), the description is adequate. It communicates the essential purpose, though it could mention what fields the profile includes. However, the simplicity of the tool makes the description sufficiently complete.

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 tool has zero parameters and the schema is empty (100% schema description coverage). Per the rubric, a no-parameter tool receives a baseline of 4. The description adds no parameter details, but none are needed.

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 a specific verb ('Get') and a clear resource ('current Yuque user profile'). It unambiguously identifies the tool's function and distinguishes it from all sibling tools, which focus on repos, docs, groups, etc.

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 usage context is implied: the agent can infer this tool is for retrieving the authenticated user's profile. However, no explicit when-to-use guidance or alternatives are mentioned. Since there is no direct sibling for this operation, the ambiguity is low, but the description still lacks explicit direction.

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