dataverse_execute_batch

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses important behavioral traits: the need for specific environment variables for write/delete operations, atomic execution with change_set_id, a maximum of 1,000 operations per request, and the return format including per-operation results.

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, well-structured paragraph that front-loads the purpose, then provides usage guidelines, requirements, and return format. Every sentence adds value without redundancy, making it concise and easy to parse.

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 complexity of batch operations, the description covers all critical aspects: purpose, when to use, environment variable requirements, atomicity, max operations, and return format. It is complete enough for an agent to understand and invoke the tool 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?

The input schema already includes detailed descriptions for each parameter (e.g., 'operations' lists minItems, max 1000; 'continue_on_error' explains behavior). The description adds value by explaining the concept of change_set_id for atomicity and the return format, which is not in the schema. Given that the schema itself is well-documented, the description provides complementary high-level context.

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 purpose: 'Execute bulk or atomic multi-operation reads and writes via the OData $batch endpoint.' It distinguishes from sibling tools by explicitly naming alternatives for single-record writes and metadata changes, and highlights the atomicity feature.

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 explicit guidance on when to use this tool (bulk operations, atomic writes) and when not to (single-record writes, metadata changes), referencing specific sibling tools. It also specifies requirements like DATAVERSE_ALLOW_WRITE and DATAVERSE_ALLOW_DELETE environment variables, and explains atomic grouping via change_set_id.

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