reopen_task

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

The description discloses the idempotent behavior, a valuable trait given the absence of annotations. It also clarifies what qualifies as a finalized task via the '[TODO]' prefix. However, it does not describe error handling or behavior for already-open tasks, leaving some ambiguity.

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 two short sentences with no redundant content. It efficiently communicates the core purpose and the idempotency feature, making every word count.

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 one-parameter mutation tool with no output schema, the description covers the essential function and behavior. It lacks details about return values or the inverse relationship with mark_task_done, but given the low complexity and self-evident purpose, it is reasonably complete.

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 schema's task_id parameter has no description (0% coverage), so the tool description must compensate. While it references 'una tarea finalizada' to imply what task_id identifies, it does not elaborate on the parameter's format, constraints, or lifecycle context. The meaning is largely inferable but minimally enriched.

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 explicitly states the action ('Reabre una tarea finalizada') and the resource (a finished task), clearly distinguishing it from siblings like mark_task_done as the inverse operation. The mention of the '[TODO]' prefix adds useful specificity.

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 implies use for reopening completed tasks but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention it is the inverse of mark_task_done. No exclusions or prerequisites are stated, so the usage context is only implied.

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