mxa_set_harm_average_count

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

The description adds no behavioral context beyond the annotations, which only indicate destructiveHint=false. It does not disclose side effects, required permissions, state changes, or any other behavioral traits that would help the agent understand the impact of invoking this 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?

The description is extremely brief (one sentence), but it is under-specification rather than effective conciseness. It fails to earn its place because it conveys no useful information beyond the tool name, making it a waste of space.

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 two parameters with zero schema coverage and no output schema documentation, the description is completely inadequate. It does not explain the tool's function, inputs, or outputs, leaving the agent with no actionable understanding.

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?

With 0% schema description coverage and no explanation in the description, the parameters 'alias' and 'params_json' remain entirely opaque. The description does not clarify what values they accept or how they affect the tool's operation, leaving the agent unable to construct valid arguments.

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] 设置谐波平均次数' is a direct translation of the tool name 'mxa_set_harm_average_count', making it a tautology. It restates the name without adding any clarifying detail, such as what a harmonic average count is or how it differs from sibling tools like mxa_set_harm_average.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or any conditions that would indicate appropriateness, leaving the agent without decision-making information.

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