rlm_task_create

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

No annotations provided, so description carries full burden. It only states it creates a task (implying mutation) but lacks details on side effects, permissions, rate limits, or what happens on failure. Minimal disclosure beyond the basic action.

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 sentences, front-loaded with identity and usage guidance. No wasted words. Efficiently conveys essential 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?

Given 9 parameters, no output schema, and no annotations, the description is incomplete. It does not cover return value, error handling, or parameter semantics beyond the sibling differentiation. Leaves significant gaps for correct invocation.

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 only 44% (4 of 9 parameters documented). The tool description does not elaborate on any parameters, leaving key fields like swarm_id and agent_id unexplained. It does not compensate for the low coverage.

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 it creates a canonical HierarchicalTask N3 work item and distinguishes from rlm_htask_create by noting it's for simple queue-style tasks vs hierarchical workflows. The purpose is specific and contrasted from a sibling.

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?

Explicitly says 'Prefer rlm_htask_create for explicit hierarchical workflows; use this for simple queue-style task creation.' This provides clear when-to-use and when-not-to-use guidance, and identifies the preferred alternative.

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