Create Task

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate these. It adds useful behavioral context by noting that the description parameter supports basic HTML/rich text and that the tool returns a compact task summary. No contradictions with the 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 four short sentences, front-loaded with the core purpose, followed by required fields, prerequisite resolution, and return format. Every sentence serves a purpose with no repetitive or unnecessary information.

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?

For an 18-parameter tool with full schema descriptions and an output schema, the description covers the essential operational details: required fields, ID resolution, HTML support, and return summary. It doesn't need to explain every parameter because the schema already does that.

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 100%, so baseline is 3. The description adds value beyond the schema by specifying which tools to use to resolve task_type_id and user IDs, and by explicitly stating HTML support for the description parameter. This helps the agent understand how to populate parameters correctly.

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 ('Creates') and resource ('one Recruit CRM task'), distinguishing it from sibling tools like search_tasks and update_task. The singular 'one' clarifies the scope, and the key required fields are listed.

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 clear operational context: it lists the required fields and tells the agent to resolve task_type_id via list_task_types and user IDs via list_users. It does not explicitly mention alternatives like update_task for modifications, but the guidance is actionable and not misleading.

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