cmw_lte_meas_fetch_frequency_error

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

With no annotations, the description carries the full burden, but it only says 'Fetch' without disclosing whether it returns cached results, performs a new measurement, or requires prior setup. This leaves the agent uncertain about side effects and data freshness.

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 short sentence with no redundant words, front-loaded with the verb and resource. It is concise and easy to scan, though it sacrifices completeness for brevity.

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 absence of annotations, output schema, and parameter descriptions, this sparse one-liner is far from adequate. It omits essential context about measurement prerequisites, return values, and how this tool fits into the LTE measurement workflow, making it nearly impossible to invoke correctly without external knowledge.

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 schema description coverage is 0%, and the description does not mention the two parameters (host, port) at all. Since there is no parameter explanation in the schema or description, the agent has no semantic understanding of how to supply these values correctly.

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 uses a specific verb 'Fetch' and resource 'LTE frequency error measurement results', which clearly distinguishes it from sibling tools like cmw_lte_meas_fetch_power or cmw_wlan_fetch_frequency_error. The purpose is unmistakable.

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 gives no guidance on when to use this tool, prerequisites such as prior configuration or triggering, or alternatives like cmw_lte_meas_fetch_all. It merely states the action without any contextual direction.

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