Api ebios rm stakeholders batch action create

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true, but the description adds nothing about what the batch actually does, whether it is reversible, what payload it expects, or what happens to objects not selected. For a non-idempotent mutation with zero extra behavioral context, this is a significant gap.

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?

A single sentence that is short but purely boilerplate – it is under-specified rather than concise. Nothing about the resource, the operation, or the expected input is front-loaded.

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?

For a mutation endpoint with no annotations beyond safety flags, no output schema, and an empty input schema, the description should clarify the action type and payload requirements; it provides none of that, leaving the agent unable to call 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?

The schema declares zero parameters (additionalProperties: false), which is itself confusing for a 'batch action' that presumably needs a payload; the description does nothing to explain how the target objects or action are supplied. With zero parameters the baseline is 4, but the unexplained empty schema and absence of any payload guidance pulls this to 3.

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 is a generic template, 'Perform a batch action on multiple objects,' and never names the resource (EBIOS RM stakeholders) nor the action being performed (delete, update, etc.). It effectively restates the name's 'batch_action_create' fragment without adding specificity, so an agent cannot distinguish it from the dozens of sibling *_batch_action_create tools.

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 guidance on when to use this batch endpoint versus the single-object siblings (ebios_rm_stakeholders_create/update/destroy) or versus other batch action tools. No prerequisites, no selection criteria, no exclusions are stated.

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