create_task

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

The description adds little beyond what annotations already convey. Annotations indicate readOnlyHint=false, which aligns with 'create', but no additional behavioral traits (e.g., permissions, side effects, idempotency) are disclosed. The description does not contradict annotations.

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?

The description is a single concise sentence with no wasted words. It is appropriately sized for a simple action, though it could be more informative without losing conciseness.

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 the 6 parameters, one required, and the existence of many sibling create tools, the description is insufficiently complete. It does not note the required company_id, the structure of the task, or how it relates to other entities, leaving the agent poorly informed.

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% and the description does not mention any parameters. With 6 parameters including ambiguous names like 'action' and 'extra_fields', the description fails to add meaning or clarify usage beyond the property names.

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 'Create a new task in Planhat' clearly specifies the verb 'create' and the resource 'task', and includes the context 'Planhat'. It distinguishes the tool from sibling create tools by resource name, but does not elaborate on the type of task or required context beyond that.

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 description provides no guidance on when to use this tool versus alternatives like create_note or create_ticket. There is no mention of prerequisites, when-not to use, or hints about the required company_id association.

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