mxa_marker_off

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

The description does not disclose what happens when markers are turned off (e.g., cleared, hidden, reset to default). With no annotations beyond destructiveHint:false, the agent lacks understanding of side effects or reversibility.

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 a single sentence, concise but under-specified. It provides no additional value beyond the tool name and does not structure information for clarity.

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 the tool has 2 undocumented parameters and an output schema (not shown), the description should address both. It does not explain return values or the effects of the parameters, leaving significant gaps for a complete tool call.

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 0%, and the description fails to explain the two parameters (alias and params_json). Their purpose and expected values are left entirely to the agent's inference, which is insufficient.

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 '[MXA] 关闭所有标记点' clearly states the action (turn off all markers) on a specific resource (markers for an MXA device). It distinguishes from sibling tools like mxa_marker_table_on, mxa_peak_search, etc., which deal with individual markers or different marker operations.

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 is provided on when to use this tool versus other marker-related siblings. For example, there is no mention of prerequisites, alternatives like turning off a single marker, or scenarios where this tool is preferred.

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