Retrieves SLA class details for application-aware routing on a specified device, helping you verify per-application path policies using a device ID or system-IP.
Get SLA class information for application-aware routing on a device.
| Name | Required | Description | Default |
|---|---|---|---|
| device_id | Yes | Device ID or system-ip |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. The verb 'Get' implies a read, but there is no disclosure of permissions, return shape, or what SLA class data includes; it adds little beyond restating the name.
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 front-loaded sentence with the resource clearly stated and no filler. It is appropriately sized, though quite thin.
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?
For a simple one-parameter read with no output schema, the description covers the basic purpose. However, with no annotations and no indication of what SLA class data is returned or when the tool is relevant, it is only minimally adequate.
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 single parameter has 100% schema description coverage ('Device ID or system-ip'), so the schema already does the work. The description adds no further detail about the parameter, making the baseline 3 appropriate.
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?
States a specific verb (Get) and a specific resource (SLA class information for application-aware routing) scoped to a device. It's clearly distinct from siblings like get_app_route_statistics in subject matter, though it doesn't explicitly name the sibling boundary.
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 when-to-use guidance, no prerequisites, and no alternatives. An agent must infer context entirely from the tool name and the SLA/routing terminology.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.