asuswrt_smart_connect_roaming_status

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

No annotations are provided, so the description carries the full burden. 'Inspect' implies a read-only, non-mutating call and the exclusions clarify what data is deliberately omitted, which is useful scope disclosure, but nothing is said about required router support, permissions, or failure behavior.

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 short sentence with no filler, front-loaded with the core resource. It is not padded, though the trailing exclusion clause is terse to the point of being slightly opaque.

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 zero-argument status tool with no output schema, the agent still does not learn what the returned state looks like (fields, enabled/disabled flags, roaming thresholds). The description is minimally adequate but leaves the return shape entirely undisclosed.

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 tool takes zero parameters, so the baseline is 4; there is no parameter semantics for the description to add or omit.

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 ('Inspect') and resource ('Smart Connect and roaming state'), and adds a scoping clause excluding steering policies and client data. It is distinguishable from siblings like asuswrt_wireless_overview or asuswrt_aimesh_status, though it does not name the alternative it is closest to.

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 explicit when-to-use, no prerequisites (e.g., that the router must have Smart Connect enabled), and no alternatives named. The exclusion clause ('without steering policies or client data') implies a narrow scope but does not tell the agent when this tool is the right pick over roughly 60 siblings.

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