batchAddEntities

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

With all annotation hints set to false, the description carries the full burden of behavioral disclosure. It only provides a return type and fails to mention crucial behaviors like whether the operation is atomic (all-or-nothing), how partial failures are handled, or what 'page operation' implies about side effects. This is insufficient for a batch mutation tool.

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 exceptionally concise: one sentence plus return type. It front-loads the core action and avoids any fluff. Every word earns its place, making it easy to parse quickly.

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 across 11 entity types, a session ID for multi-browser routing, and sibling single-entity functions), the description is underpowered. It does not explain error handling, atomicity, or clarify when to use batch vs. individual adds. The output schema covers return values, but usage context is severely lacking.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds minimal semantics beyond what the schema already provides, except for the phrase 'one page operation,' which suggests batch atomicity but is ambiguous. It does not deepen understanding of the parameters themselves.

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 action 'Add multiple supported entities in one page operation', which is specific enough to understand the tool's purpose and differentiates it from single-entity sibling tools like addMarker or addLabel by using 'batch' and 'multiple'. However, 'supported entities' is vague without the schema, and an explicit comparison to the add* functions would have been stronger.

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 tool versus the individual add* functions. The phrase 'one page operation' hints at a key use case (e.g., atomic batch adds), but this is never explicitly stated. No alternatives or exclusions are mentioned, leaving the agent to guess when this is the right choice.

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