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 of behavioral disclosure, yet it says nothing about side effects, permissions, whether the profile must be active, or what happens to the task afterward. For a mutation tool with zero annotation coverage, this is effectively no transparency.

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?

One short sentence with no filler, which is appropriate in size, but the brevity comes from vagueness rather than precision — the front-loaded content is a metaphor that does not identify the operation cleanly.

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?

With no annotations, no output schema, and an empty parameter schema, the description is the only source of information and it does not explain what gets created, where it lands, or what the caller must provide. Far too little for a write operation in a task-management family.

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 tool takes no parameters and schema coverage is 100%, so the baseline is high. However, the description implies inputs that the empty schema cannot supply ('a profile's list', and the now-vs-later choice), and it never explains how those are specified, leaving a real ambiguity.

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 restates the name in metaphor: 'put work on a profile's list' means adding a task, but the resource ('work') and container ('list') are never stated plainly, and it gives no differentiation from siblings like task.start, task.list, or task.done. An agent must guess that this creates a queued task rather than executing one.

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?

There is no guidance on when to use this versus task.start or task.list. The fragment 'for now or for later' faintly implies a scheduling choice but is too vague to route the agent, and no prerequisites or alternatives are named.

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