Maa Install

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

With no annotations, the description bears the full disclosure burden. It says nothing about what gets downloaded, whether existing files are overwritten, network or permission requirements, or the operation's reversibility — significant gaps for an install/mutation 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 the action and resource front-loaded and a parenthetical qualifier that earns its place. No filler or redundancy.

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-value detail is not needed, and a zero-param tool keeps the surface small. However, for a first-run install the description omits prerequisites and any note on relationship to maa_update_core, leaving the agent guessing about sequencing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-level misunderstandings are possible.

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 a specific verb (安装/install) and concrete resource (MaaCore 及资源), so the agent knows exactly what the tool does. It does not explicitly distinguish itself from close siblings like maa_update_core or maa_install_cli, though the 'first use' note hints at the boundary.

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?

The parenthetical '(首次使用需要)' gives an implied condition for use — first-time setup. It does not tell the agent when to prefer this over maa_update_core or maa_install_cli for subsequent/CLI scenarios, leaving the alternatives unaddressed.

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