promote_task

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

Describes the creation of a full task file with YAML frontmatter and dependencies. However, it omits key behavioral details such as whether the backlog entry is removed or updated, and there are no annotations to supplement safety or side-effect information.

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?

Two concise sentences that front-load the core purpose and function. Every word contributes value, with no redundancy or irrelevant 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?

Given 6 parameters, no output schema, and no annotations, the description provides adequate context for the basic operation but lacks details on return values, error handling, and the fate of the backlog entry. Slightly incomplete for a tool with moderate 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?

Schema coverage is 100%, so the baseline is 3. The description adds context about the overall action (e.g., creating a full task file) but does not elaborate on individual parameters beyond what the schema provides. This meets the minimum for a well-covered schema.

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 specific action (promote), the resource (task from BACKLOG.md to active YAML file), and distinguishes from sibling tools like add_to_backlog or create_task by focusing on promotion rather than creation or addition.

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?

Provides explicit usage context: 'Use this when starting work on a backlog item.' This guides the agent on when to invoke. However, it does not mention when not to use it or suggest alternatives, which would strengthen the guidance.

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