batch_operations

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

No annotations are present, so the description carries the full burden; it discloses no behavioral traits such as mutation, deletion risk, connection preservation, or required prerequisites. The description is completely opaque about side effects.

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 short phrase, which is concise, but it is under-specified rather than efficiently informative. It omits essential operational details.

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 5 parameters, nested objects, no output schema, and no annotations, the description fails to explain the operation types, options, or side effects, making the tool's behavior largely obscure and incomplete.

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 100% for top-level parameters, so the baseline is 3. The description adds no extra parameter context, and nested properties like size/position lack descriptions, but the schema already provides meaningful top-level descriptions.

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 '批量操作图表元素' (batch operations on diagram elements) identifies a resource and a broad action, but 'batch operations' is not a specific verb and the tool's actual operations (create, update, delete, etc.) are left to the schema. It does not distinguish this tool from siblings like batch_import or copy_paste.

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?

There is no guidance on when to use this tool versus individual element operations or batch_import. The description is only a noun phrase and provides no context or alternatives.

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