Maa Recruit All

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

No annotations are provided, so the description carries the full burden. It implies significant side effects (it starts new recruitment jobs) but says nothing about ordering of collect-then-start, what happens when there are no results, whether it blocks, or what failure looks like — all important for a state-changing tool.

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?

A single short sentence with both actions front-loaded and zero filler. Nothing to trim.

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 needn't be explained. However, for a composite mutation tool with no annotations, the definition leaves behavioral gaps — sequencing, idempotency, and failure behavior — that an agent would want before calling it.

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 100% for the single 'client' parameter, so the schema already documents it. The description adds no meaning about the client parameter or its default, which is acceptable under the high-coverage baseline but yields no extra value.

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 two concrete operations — collecting all recruitment results and starting a new recruitment — so the agent knows exactly what the tool performs. It is clear on verb and resource, but it never mentions it is a composite of maa_recruit_collect and maa_recruit_start, which are both siblings, so the differentiation is left implicit.

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?

"一键" (one-click) implies this is the convenience path versus doing collect and start separately, but the description never says when to prefer it over maa_recruit_collect or maa_recruit_start, nor any preconditions. Usage is only implied, not stated.

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