execute_collaborative_task

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

No annotations provided, and the description barely adds behavioral context beyond 'execute'. It does not disclose side effects, idempotency, error handling, or authorization needs.

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 extremely short but under-specified; it does not provide enough information to be considered efficiently concise. It omits critical details that could be included without adding length.

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 one parameter, no output schema, and abundant sibling tools, the description is incomplete. It does not explain return values, execution semantics, or interactions with other tools.

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 coverage is 0%, and the description only repeats the parameter name 'task_id' and its role (任务ID). No additional meaning or format constraints are given beyond the schema.

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 states the tool executes a multi-robot collaborative task, which distinguishes it from siblings like 'create_collaborative_task' (creation) and 'setup_multi_robot_coordination' (setup). However, it lacks detail on what constitutes a collaborative 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?

No guidance on when to use this tool versus alternatives, no prerequisites (e.g., task must exist), and no context on preconditions or failure modes.

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