workiva_wdata_list_queries

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

No annotations are provided, and the description does not disclose any behavioral details beyond the basic action. It lacks information about pagination, ordering, authentication requirements, or what exactly constitutes a 'query' in this context, so the agent has no additional safety or behavior 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 very short and front-loaded with the purpose. The Args section is compact. It is appropriately sized for a simple tool, though the brevity leaves out important context.

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?

Despite the simplicity of the tool, the description lacks essential context about the Wdata domain, such as whether queries are workspace-specific, organization-wide, or what 'query' refers to. The existence of an output schema doesn't compensate for the missing domain context, making it under-specified for an agent unfamiliar with the system.

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 description mentions 'max_results' with 'Max results to return', which is redundant with the parameter title in the schema. With 0% schema description coverage, the description adds minimal value and fails to clarify semantics like default behavior, limits, or how results are ordered.

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 'List Wdata queries' uses a clear verb with a resource, which is straightforward. It distinguishes itself from siblings like get_query (which retrieves a single query) by the verb 'list'. However, it doesn't add any scope or domain context that would differentiate it further from other list operations in the sibling set.

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 alternatives such as get_query, create_query, or other list tools. It doesn't mention typical scenarios or exclusions, leaving the agent without direction for tool selection.

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