workiva_wdata_get_query

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

With no annotations, the description carries the full burden of behavioral disclosure, but it merely restates the tool's name. It does not indicate that this is a read-only operation, what kind of data is returned, or any required permissions, adding no meaningful behavioral context.

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 single-purpose sentence and a minimal Args block. Every word earns its place; no filler or redundancy. The structure is clean and easy to parse.

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?

Though an output schema exists, the description is too terse to be contextually complete. It does not explain what a 'query' is in Wdata, what information is retrieved, or how this tool relates to sibling query operations (e.g., describe_query, validate_query). The single sentence leaves the agent with insufficient context for confident selection.

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 Args section ('query_id: The query ID') simply restates the schema property title 'Query Id' and the property name query_id, adding no additional semantic value. The parameter is self-explanatory, but the description does not enrich or clarify it beyond what the schema already provides.

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 tool's function with a specific verb ('Get') and a specific resource ('a single Wdata query'), distinguishing it from sibling tools like list_queries, create_query, or delete_query.

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. There is no mention of prerequisites, typical use cases, or exclusions, leaving it to the agent to infer when 'get' is appropriate.

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