cmw_lte_configure_bearer

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

With no annotations provided, the description must communicate behavioral traits. It only says 'Configure', indicating a mutation, but gives no details about side effects, required prior setup (e.g., LTE cell must be on), or whether changes are reversible. It also omits any mention of return values or errors, leaving the agent uncertain about the operational impact.

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, focused sentence that immediately conveys the core action and objects ('Configure default EPS bearer (APN and IP version)'). It contains no filler or redundant details, making it highly efficient and front-loaded.

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 four parameters, no output schema, and no annotations, yet the description provides only a minimal overview. It does not explain the purpose of host and port, specify expected outcomes, or describe any operational constraints. For a configuration tool with this complexity, the description is insufficiently complete to guide correct invocation.

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 description mentions 'APN and IP version', which maps to the apn and ip_version schema parameters, but these already have descriptions in the schema. The host and port parameters have no descriptions in either the schema or the tool description, and the description does not clarify their role or relationship to the bearer configuration. With 50% schema coverage and no compensating explanation, the semantics for half the parameters remain ambiguous.

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 clearly states the verb 'Configure' and the specific resource 'default EPS bearer', while explicitly listing 'APN and IP version' as the configurable aspects. This distinguishes it from sibling LTE tools like cmw_lte_configure_cell (cell configuration) and cmw_lte_configure_nas (NAS configuration), which address different configuration targets.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention any prerequisites, exclusions, or typical scenarios. The only hint is the tool name and the phrase 'default EPS bearer', which implies a specific context but offers no actionable direction.

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