workiva_wdata_upload_file

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

With no annotations provided, the description carries the full burden of disclosing side effects and behavior. It merely states 'Upload a local file to Wdata' without explaining what happens on success, whether it overwrites existing files, or any error conditions. This is a significant transparency gap for a 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 extremely concise, with a clear action statement and a compact argument list. It wastes no words and is front-loaded with the core purpose, making it easy to scan.

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 simple one-parameter upload tool, the description covers the basic action but omits return behavior, prerequisites, and potential side effects. While an output schema exists (not shown), the description still lacks enough context for an agent to fully anticipate the tool's behavior in a workflow.

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 provides only a bare 'File Path' string, so the description's 'Local file path (absolute)' adds crucial constraints (local filesystem, absolute path) that are not present in the structured schema. For a single parameter, this is useful and compensates reasonably for the 0% schema description coverage.

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 uses a clear verb ('Upload') and resource ('local file to Wdata'), accurately distinguishing it from sibling tools like workiva_wdata_get_file or workiva_wdata_delete_file. The action is specific and leaves no ambiguity about what the tool does.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context (e.g., needing a table or connection first). With many sibling tools, this omission leaves the agent without a clear decision framework.

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