yuque_create_resource

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

Despite having no annotations, the description does not address behavioral traits such as side effects, authorization needs, or what happens when doc_id/url is omitted (the resource may not be attached to a document). The description only mentions supported types, leaving significant behavioral gaps.

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 very concise with two sentences. The first sentence states the purpose, and the second adds critical detail about the supported resource types. Every sentence serves a purpose without redundancy.

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?

The tool has 6 parameters and no output schema. The description does not explain the behavior when doc_id/url are omitted, the meaning of insert_after_lake_id, or what the tool returns. This leaves significant gaps for a complex 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 coverage is 100% with detailed descriptions for all parameters. The description adds minimal value beyond the schema, only clarifying that resource_type is limited to 'board' and listing the board types. Baseline 3 is appropriate.

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 creates a structured resource in a Yuque document and specifies that resource_type only supports 'board' with subtypes mindmap, flowchart, or architecturediagram. This clearly distinguishes it from sibling tools like yuque_create_doc or yuque_create_book.

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 explicit guidance on when to use this tool versus alternatives like yuque_create_doc. The name and description imply it's for creating resources within a document, but it does not state when to prefer this over other create tools or how it relates to them.

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