Maa Recruit Start

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says "start". It does not disclose that this is a mutating in-game action, whether it consumes resources, what happens if a recruitment is already in progress, or what permissions/connection state are needed.

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 single four-character phrase is not concise-but-complete; it is under-specification. There is no front-loaded scope, no key constraint, and no routing information – nothing that earns its place beyond the tool name.

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?

An output schema exists so return values need not be explained, and parameters are fully documented in the schema. But with zero annotations and no usage context, the definition leaves an agent unable to tell when this action should fire relative to its recruit siblings or what state it requires.

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%, with tags, time and client all documented with examples (including the 300/1800/7200/28800 time mapping). The description adds nothing beyond the schema, so the baseline 3 applies.

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?

"开始公招" only restates the tool name maa_recruit_start – a start verb plus the same resource. It conveys no scope, no distinction from siblings like maa_recruit_get, maa_recruit_collect or maa_recruit_all, so an agent must infer what starting a recruitment actually entails.

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?

There is no guidance on when to call this versus the three sibling recruit tools (get/collect/all), no mention of prerequisites such as the game client running or MAA being connected. The agent is left to guess at ordering within a recruitment workflow.

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