batch_classify

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

No annotations are provided, and the description lacks behavioral details such as error handling, rate limits, synchronous/asynchronous behavior, or any constraints on input size. The description only states the core function without any additional context.

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 sentence that is front-loaded and contains no redundant information. It is as concise as possible while conveying the essential purpose.

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 batch operation complexity and existence of an output schema, the description is adequate but missing details like maximum batch size, whether processing is synchronous, or how errors are handled for individual texts. The output schema may cover return values, but constraints are omitted.

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%, and while the description adds no extra meaning beyond the schema, the schema itself is clear. Baseline 3 is appropriate as the description does not enhance parameter understanding beyond what the schema provides.

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 'Classify multiple texts at once' clearly states the verb (classify) and resource (multiple texts), distinguishing it from the sibling tool 'classify_text' which is for single text classification.

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 implies use for batch classification, but does not explicitly state when to use it versus alternatives like 'classify_text' for single texts or 'batch_add_custom_categories'. No when-not or prerequisite guidance is provided.

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