workiva_list_tasks

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

Neither annotations nor the description disclose safety or side-effect information. The description only says 'List' which implies read-only, but it doesn't mention pagination, ordering, or any limits beyond the max_results parameter. Since there are no annotations, the description carries the full burden and fails to provide meaningful transparency.

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 sentence for the purpose and two lines for parameters. No filler or redundancy, making it 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?

For a list tool with just two parameters and an output schema, the description is somewhat incomplete: it doesn't specify how the workspace is selected or any behavior regarding the result set (e.g., capped at max_results). However, the presence of an output schema reduces the need to explain return values, and the simple parameter list keeps the description reasonably adequate.

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 explains filter as an OData filter with an example, adding value beyond the schema's bare property names. max_results is described as 'Max results to return', which is only slightly more informative than the title. Given 0% schema description coverage, the compensation is minimal but present.

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?

States 'List tasks in the workspace' with a specific verb and resource, clearly distinguishing from related task operations like workiva_get_task or workiva_create_task. The description is unambiguous about the tool's core function.

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?

No explicit guidance on when to use this tool versus alternatives such as workiva_get_task or other list tools. The verb 'List' implies enumeration, but the description doesn't mention exclusions or prerequisites, leaving usage inferred.

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