workiva_reject_task

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

With no annotations, the description carries the full burden of explaining behavior. It simply states 'Reject a task' without disclosing what rejection entails, whether it is reversible, what permissions are required, or any side effects. This is a significant gap for an action that likely mutates task state.

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 compact: a single sentence stating the action plus an Args block for the parameter. Every word serves a purpose, and it is front-loaded with the core intent. There is no redundancy or unnecessary detail.

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?

The description lacks any surrounding context needed for a task action, such as the relationship to other task states (submitted, approved, reassigned), consequences of rejection, or typical usage scenarios. Even though an output schema exists, the description itself is too thin to enable confident tool selection in a complex 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 description adds the clarification 'The task UUID' to the task_id parameter, which goes beyond the schema's generic 'Task Id' title. However, it does not provide further context such as how to obtain the UUID or any constraints, so the value added 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?

The description uses a specific verb and resource ('Reject a task'), clearly distinguishing it from sibling tools like approve_task, submit_task, and reassign_task. Despite its brevity, the purpose is unambiguous and immediately actionable.

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 such as approve, submit, or reassign. There is no mention of workflow states, prerequisites, or conditions under which rejection is appropriate, leaving the agent to infer usage solely from the tool's name.

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