batch_request

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

The description explicitly states the tool can execute POST, PATCH, and DELETE methods, but the annotations declare readOnlyHint=true. This is a direct contradiction: a read-only tool cannot perform write operations. The description and annotations are irreconcilable, severely undermining trust and safety.

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 two sentences long, front-loaded with the core purpose, and includes only essential details (method, URL, body, max operations). No wasted words or redundancy.

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 (batch operations with multiple HTTP methods), the description covers the basics but omits important behavioral details such as response format, ordering guarantees, partial failure behavior, and correlation via operation IDs (which the schema partially addresses). The annotation contradiction further exacerbates the overall incompleteness.

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 schema provides 100% coverage with detailed descriptions for operations, id, method, url, and body. The description adds the 50-operation limit and mentions optional body, but these are already captured in the schema via maxItems and the body property. The description adds minimal value beyond the schema.

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 executes multiple ServiceNow REST API operations in a single HTTP call, which is a specific verb+resource combination. It distinguishes itself from the many individual operation tools in the sibling list by focusing on batching.

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 when to use this tool by noting it reduces round-trips by 50-70% and has a maximum of 50 operations per batch. This gives clear context for batching multiple operations but does not explicitly name alternatives or state when not to use it.

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