batch_import

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only states 'Batch import chart files'. It omits critical side effects such as file overwriting, backup creation, format validation, and permission requirements, all of which are specified in the schema options.

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 with no redundancy, making it concise and easy to parse. However, it is so brief that it borders on under-specification, though this is better addressed in other dimensions.

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 (5 parameters including nested objects) and the absence of an output schema or annotations, the description fails to convey return values, error behavior, or operational context. It is insufficient for an agent to fully understand the tool's capabilities and side effects.

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 descriptions for all parameters, so the tool description adds no additional parameter semantics. The baseline of 3 applies because the schema already effectively documents all parameters and their options.

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 import chart files' clearly states a batch import function for diagram files. The verb 'import' and resource 'chart files' distinguish it from siblings like load_diagram and create_diagram, though it could more explicitly mention the source directory context.

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 provides no guidance on when to use this tool versus alternatives like load_diagram or batch_operations. There is no mention of prerequisites, exclusions, or scenarios where this tool is preferred, leaving the agent to infer usage from the name alone.

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