score_batch

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'sequentially' and the batch limit, but does not disclose side effects, error handling, rate limits, or the meaning of the continue_on_error parameter. This leaves the safety profile and failure behavior unclear.

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 front-loads the action and a key constraint (limit of 25). It contains no unnecessary words and is appropriately sized for a simple tool.

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?

Even with an output schema present, the description omits critical context: what each workflow item should contain, how errors are handled, and the effect of continue_on_error. For a tool with two parameters and no schema descriptions, this level of detail is insufficient for an agent to invoke it 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?

Schema description coverage is 0%, and the description does not explain the 'items' array structure or the 'continue_on_error' parameter. The item objects are only typed as additionalProperties: true, leaving the agent without any guidance on required fields or formats.

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's function ('Score up to 25 workflow items sequentially in one request') and includes the endpoint, which distinguishes it from the sibling tool score_workflow. The action and resource are specific and unambiguous.

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 usage when you have up to 25 workflow items to score in a single request, but it does not explicitly contrast with score_workflow or state when to prefer one over the other. No alternatives or exclusions are mentioned, so guidance is only implicit.

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