Api chat agent runs batch action create

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, and the description adds nothing beyond that: it doesn't say whether the call is all-or-nothing, what happens to objects that fail, or whether destructive actions can be routed through it despite destructiveHint=false. For a mutation endpoint this leaves the behavioral picture thin.

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?

One sentence, front-loaded, no filler — but it is short because it omits essentials rather than because it is dense with meaning. Brevity at the cost of disambiguation isn't true conciseness.

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?

A mutating, non-idempotent batch endpoint with no output schema and an empty request schema needs the description to explain the action vocabulary and payload shape; instead it offers a single generic sentence. An agent has essentially nothing to act on beyond the name.

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 declares zero parameters with additionalProperties=false, so per the baseline rule a 3-4 is warranted. However, the description's phrase 'multiple objects' implies object identifiers and an action selector that the empty schema does not expose, so it raises a question it never answers rather than clarifying inputs.

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?

It gives a verb and a resource ('perform a batch action on multiple objects'), but the resource is generic boilerplate shared by dozens of sibling *_batch_action_create tools, so an agent cannot tell from the text that this one targets chat agent runs. The tool name carries the actual scoping, not the description.

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?

There is no statement of when to use this versus a per-object endpoint (e.g. chat_agent_runs_cancel_create) or versus the many other batch_action siblings. No prerequisites, no mention of what kinds of actions are supported or when the operation is appropriate.

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