superpos_create_task

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

Discloses it creates tasks for other agents and routing options, but no mention of side effects, permissions, or other behavioral traits. No annotations so description carries burden.

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 main action, then specific guidance. Efficient but could include brief parameter hints without being verbose.

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?

Moderately complex tool with 9 params and no annotations; description covers main use but lacks detail on many parameters. Output schema exists but is separate.

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?

Only clarifies instructions and payload parameters; other 7 parameters (hive_id, priority, etc.) are unexplained. Schema coverage is 0%, so description should compensate more.

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?

Clearly states 'Create a task in the hive for another agent to pick up', specifying the verb (create), resource (task in hive), and distinguishes from siblings like get_task or complete_task.

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 guidance on using instructions vs payload, and routing with target_capability or target_agent_id. Lacks explicit when-not-to-use or alternatives, but is adequate.

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