approve_task

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

No annotations are provided, so the description carries full burden. It discloses that approval triggers human expert work and may take hours, which is a key behavioral trait. However, it does not mention any side effects, reversibility, or error states beyond the confirmation.

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 concise, with a clear opening sentence followed by usage context in a separate paragraph, and standard Args/Returns sections. No unnecessary information is present.

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 simple tool with one parameter and an output schema, the description adequately covers what the tool does, when to use it, and the parameter. It could mention idempotency or error conditions but is largely complete given the tool's complexity.

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 the task_id parameter as 'The Tendem task ID (UUID) to approve.', adding semantic detail beyond the schema's type definition. This helps the agent understand the expected format and purpose.

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 action 'approve' and the resource 'Tendem task and its price', distinguishing it from sibling tools like cancel_task, create_task, etc. It also specifies the resulting behavior (human expert begins working).

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 tells when to use the tool: after reviewing the price in AWAITING_APPROVAL status. It also explains the expected outcome (human works for hours). However, it does not explicitly mention when not to use or provide alternative tools, but the context is clear.

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