ctx_task

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about what claiming does (locking, exclusivity, conflicts), whether release undoes a claim, what recovery follows a failed complete, or any permission requirements. 'complete needs evidence' is the only real behavioral disclosure.

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?

Extremely compact and front-loaded with the action verbs, so no sentence is wasted. However, at this level of compression for a 5-parameter mutating tool the terseness shades into under-specification.

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?

A concurrency-sensitive task-mutation tool with 5 params, zero schema descriptions, no annotations, and no output schema needs substantially more than 8 words. An agent cannot tell what a successful claim returns or how conflicts are surfaced.

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% across 5 parameters, so the description must compensate, and it only partially does. It implies the action enum values and flags evidence for complete, but says nothing about the required agent or task_id, nor about the optional project.

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?

Names three specific verbs (claim, release, complete) against one resource (a task), which is enough to distinguish it from read-oriented siblings like ctx_get/ctx_search. The pipe-delimited form and lack of any scope statement keep it from a 5.

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 only guidance is that 'complete' requires evidence, which is a precondition rather than a when-to-use statement. It never says when to claim vs. release, or how this relates to the mutation-flavored sibling ctx_commit.

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