Create task

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

No annotations are provided, so the description bears the full burden. It only says 'Create a new task' without any behavioral details such as side effects, visibility of created tasks, or permission requirements. The minimal description lacks transparency for an 11-parameter tool.

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 efficient sentences: purpose first, then guideline. No waste, but it could be slightly more informative without harming brevity.

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 11 parameters, no output schema, and no annotations, the description is insufficient. It doesn't explain the creation process, return value, or the effect of optional parameters. The duplicate-check advice is helpful but not enough for a tool of this 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?

The description does not add any parameter-level information beyond what the input schema provides. Schema coverage is 55%, but the tool description fails to clarify any parameters, leaving agents to rely solely on the schema's incomplete descriptions.

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 'Create a new task' with a specific verb and resource, and it distinguishes from sibling tools like sp_update_task, sp_delete_task, etc.

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 guidance: 'Search with sp_list_tasks first to avoid creating duplicates of an existing task.' This tells the agent when to use the tool and a pre-condition, though it doesn't mention when not to use it or compare with alternatives.

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