yuque_update_toc

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 a generic 'update' operation, without disclosing that the tool actually supports multiple actions (append, prepend, insert, move, remove, edit) that go beyond simple updates. Mutation traits and potential side effects are not addressed.

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 concise in length (one sentence) but is under-specified, which undermines its usefulness. It does not include any additional structured information or elaboration that would help an agent invoke the tool correctly, making it unhelpfully terse rather than effectively concise.

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 complexity (13 parameters, 3 enums, multiple action types), the description is completely inadequate. It lacks any explanation of required parameters, action modes, or expected behavior, and there is no output schema to clarify return values. The description does not nearly provide enough context for an agent to use this tool correctly.

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 description provides no information about the 13 parameters. Since schema description coverage is 0%, the description fails to compensate by explaining what any of the parameters (e.g., action, node_type, target_uuid) mean or how they relate to the tool's behavior.

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 'Update Yuque repository TOC nodes' uses a specific verb and resource, clearly indicating it modifies the table of contents of a Yuque repository. It distinguishes from sibling tools like yuque_get_repo_toc (which retrieves) and yuque_create_document_with_toc (which creates), so the core purpose is clear.

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. The description does not mention any use cases, prerequisites, or exclusions, leaving the agent without context for selecting this tool over others like yuque_update_repo or yuque_get_repo_toc.

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