mxa_query_frequency

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

Annotations already declare readOnlyHint=true, so the tool is known to be non-destructive. However, the description adds no additional behavioral context (e.g., what is queried, side effects, performance implications). It adds no value beyond the annotation.

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 short (one phrase), but this is under-specification rather than conciseness. It lacks critical information and does not earn its place; more detail is needed to be useful.

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 output schema exists (not shown) and parameters are optional, the description should at least hint at what the query returns or how parameters affect it. It fails to provide a complete picture, especially with 0% schema description coverage.

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 does not explain the two parameters 'alias' and 'params_json'. Their defaults and possible values are not clarified, leaving the agent without guidance on how to populate them meaningfully.

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 '查询频率参数' (Query frequency parameters) vaguely indicates the tool queries frequency-related parameters, but does not specify what exactly is queried (e.g., current settings, measurement results). Among many sibling MXA tools, it is not clearly distinguished from similar query tools like mxa_query_sweep_time.

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 alternatives. In a large set of sibling tools including mxa_set_frequency and mxa_query_sweep_time, there is no differentiation or usage context, forcing the agent to guess.

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