reject_task

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

The annotations already state destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds only an HTTP endpoint and does not explain what gets rejected, whether the rejection is reversible, what permissions or task states are required, or what side effects occur.

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 no wasted filler. However, for a destructive, non-idempotent mutation, this level of terseness is under-specification rather than effective conciseness.

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 tool has two required parameters, no output schema, and destructive annotations, so the description should carry more behavioral and usage context. It provides only a restated name and endpoint, leaving critical information about task rejection semantics, preconditions, and effects entirely absent.

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?

Schema description coverage is 0%, so the description must compensate, but it only places project_id and task_id in a URL path. It does not clarify that project_id identifies the project and task_id identifies the task within it, nor any constraints beyond what the schema already declares as integer minimum 1.

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 says only "Reject Task. POST /project/{project_id}/tasks/{task_id}/reject." This largely restates the tool name and gives an HTTP endpoint, without explaining what rejecting a task actually means, what state it applies to, or how it differs from siblings like confirm_task, stop_task, or delete_task.

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 reject_task versus confirm_task, stop_task, delete_task, or wait_for_task. The description provides no prerequisites, exclusions, or decision criteria, leaving the agent to infer usage from the name alone.

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