workiva_wdata_batch_refresh_connections

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

With no annotations, the description carries full burden for behavioral disclosure. It reveals that the old endpoint is dead and this fans out, and that it aggregates results. However, it does not disclose failure modes, partial success handling, idempotency, or any side effects beyond refreshing. This is minimal behavioral context 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 concise and well-structured: it opens with the core purpose, explains the deprecated endpoint issue, and closes with an Args section. It avoids fluff and each part serves a purpose, though the Args section could be slightly more detailed.

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 simplicity (one optional param) and the presence of an output schema, the description provides the necessary context: what it does, why it exists, and the input. However, it omits details about error handling, partial failures, or how results are aggregated, which could be important for a batch operation. This keeps it at a minimum viable level.

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 has one parameter, connection_ids, with 0% description coverage. The description adds a one-line Args section ('List of connection IDs to refresh'), but it essentially restates the parameter name and provides no additional formatting, requiredness, or edge-case guidance. This does not adequately compensate for the missing schema documentation.

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 verb ('Batch refresh') and resource ('multiple Wdata connections') with a specific mechanism ('fanning out to the per-connection endpoint'). It also distinguishes itself from the sibling workiva_wdata_refresh_connection by clarifying it's a batch operation and notes the deprecated endpoint is dead.

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 explains the context: the old batch endpoint is dead and this function now fans out to the working per-connection endpoint. It references the sibling workiva_wdata_refresh_connection as the base endpoint, implying this is the batch version. It doesn't explicitly state exclusions (e.g., not for single connections), but the name and 'batch' wording make the usage clear.

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