Router factory login (manufacturer-cited)

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

With no annotations, the description carries the burden and does disclose notable behavior: results are cited to manufacturer documentation with the source URL, coverage is bounded to the 409-model ssid.ai directory, and the tool will report the absence of a default password rather than failing. It does not state error behavior for unknown models or any rate/auth constraints, so it falls short of a 5.

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?

It front-loads the returned data, then the input modes, then usage triggers and scope limits; every sentence contributes. It is dense and slightly run-on but contains no filler or repetition.

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?

With no output schema and no annotations, the description supplies the return payload contents, the sourcing guarantee, and the directory-size limit, which is enough for correct invocation. It stops short of describing failure behavior when the slug or brand/model is unmatched.

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 description coverage is already 100%, so the baseline is 3, but the description adds real meaning by explaining the two alternative input modes ("Pass the ssid.ai slug, or brand plus model") — an exclusivity/combination rule the schema lists only as separate optional properties.

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 names a specific resource (router/gateway default credentials and factory-reset data) and enumerates exactly what is returned: gateway IP, admin username/password or its absence, credential type, and reset steps. It is clearly distinguishable from siblings like lookup_mac and check_router_compliance without opening any schema.

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?

It gives explicit trigger conditions ("after lookup_mac identifies the vendor, or whenever a user asks for a router's default login, factory password, gateway address or reset procedure") and an explicit exclusion ("no listing or wildcard search"), plus the input-mode rule (slug or brand plus model). This is a full when/when-not/alternative disclosure.

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