cmw_lte_meas_fetch_sem

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

No annotations are provided, so the description carries full burden. It merely restates the action implied by the name ('Fetch') without disclosing behavior such as whether the tool triggers a measurement, returns previously captured results, or requires prior setup. No added behavioral context beyond a simple read operation.

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?

A single, clear sentence with no wasted words. It is front-loaded and effectively communicates the core purpose.

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?

The tool has no output schema, no annotations, and undocumented parameters. The description is too minimal to enable correct invocation; it omits connection semantics, return format, and any measurement workflow context.

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 has two parameters (host, port) with 0% schema description coverage, and the description provides no explanation of their meaning. The agent is left without any information about what host/port refer to, how they are used, or their formats.

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 the specific verb 'Fetch' and identifies a precise resource: 'LTE SEM (Spectrum Emission Mask) measurement results.' This clearly distinguishes it from sibling fetch tools like power, EVM, or ACLR.

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?

There is no guidance on when to use this tool versus alternatives, such as cmw_lte_meas_fetch_all or cmw_meas_fetch_spectrum. The description does not mention prerequisites like previous configuration or triggering, nor does it exclude other tools.

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