cmw_lte_meas_fetch_aclr

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Fetch' without explaining whether a measurement must be triggered first, whether it is read-only, or what happens with stale data. Minimal transparency beyond the action itself.

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?

Single sentence with no redundant wording, front-loads the key action and measurement type. However, it omits needed context, so conciseness is good but not exemplary.

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's role in a measurement workflow, the description doesn't mention the need for prior configuration/trigger or any connection details. It is minimally viable but lacks operational context to be used correctly.

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 describes host and port with zero descriptions, and the description does not explain their purpose. With 0% schema coverage, the description fails to compensate for the missing parameter semantics, leaving the agent without any meaning for the two parameters.

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?

Description uses specific verb 'Fetch' with resource 'LTE ACLR measurement results', clearly distinguishing it from sibling fetch tools for other measurements (power, EVM, SEM, etc.). The acronym expansion further clarifies the measurement type.

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 on when to use this tool versus alternatives like cmw_lte_meas_fetch_all or other measurement fetches. No mention of prerequisites such as configuring and triggering the ACLR measurement first, which is critical in a measurement workflow.

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