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

No annotations are provided, so the description carries the full burden. It discloses that the tool is deprecated and is a shim that dispatches to the named tools, which is useful behavioral context. However, it does not describe what operations it supports, how it maps to the target tools, or any side effects or limitations, leaving significant gaps.

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 very concise: two sentences, with the DEPRECATED warning front-loaded and the replacement tools listed. It wastes no words. However, it is structured as a single paragraph and could have been improved with a brief note on parameter meaning without harming 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?

Given the tool has 3 parameters with 0% schema coverage and no annotations, the description is too thin. It successfully redirects users to the modern tools, but it does not explain the shim's own interface or valid operations. As a deprecation notice it is adequate, but as a tool description it leaves questions about invocation and parameter semantics unanswered.

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?

Schema description coverage is 0% and the description does not mention any of the three parameters (operation, connection_id, connection_ids). It provides no explanation of how these parameters are used or how they relate to the dispatcher behavior. The description adds zero value beyond the raw schema.

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 identifies this tool as a deprecated backward-compatibility shim and names the specific tools it dispatches to. While its own function is not explicitly described as 'list/get/refresh connections', the reference to the single-verb tools makes its purpose clear, and it distinguishes itself from siblings by naming replacements.

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 explicitly instructs to use the alternatives ('use workiva_wdata_list_connections / workiva_wdata_get_connection / workiva_wdata_refresh_connection / workiva_wdata_batch_refresh_connections') and states it is only kept for backward compatibility. This provides clear when-to-use and when-not-to-use guidance, fully differentiating it from the alternatives.

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