hub_task_add

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects, permission requirements, return values, or what 'shared cross-project backlog' implies behaviorally. This is minimal for a create operation.

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?

A single, front-loaded sentence that states the tool's purpose without any waste. It is appropriately sized for a simple add-operation tool.

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 schema provides good parameter coverage, but the overall context is thin: no output schema, no behavioral notes, and no error semantics. For a tool that creates a task, the description should indicate what happens on success (e.g., returns a task ID) and any constraints. It is only minimally adequate.

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 adds no parameter information, but the schema provides meaningful descriptions for 7 of 9 parameters (78% coverage), including 'by', 'cat', and 'importance'. The schema carries the parameter semantics, so the description need not compensate.

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 uses a specific verb ('Add') with a clear resource ('task') and context ('shared cross-project backlog'), distinguishing it from siblings like hub_task_update and hub_task_list.

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?

Usage is implied by the action ('Add a task'), but there is no explicit guidance on when to use this tool versus alternatives, such as hub_task_update for modifications or hub_queue_send for messaging. No exclusions or prerequisites are mentioned.

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