router_profile_check

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

No annotations are supplied, so the description carries the burden. 'Inspects' implies a read-only operation and the text explains the safety intent, but it doesn't say whether a failed check returns an error, a boolean, or a warning string, nor whether it blocks anything. That is real additional context, but the behavioral disclosure stays at a basic level.

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?

Two short sentences: the purpose and what it inspects come first, and the prescriptive 'use before' guidance follows. No filler, and a reader gets the gist from the first line.

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?

Since an output schema exists, the description doesn't need to explain return values, and with zero parameters the surface area is small. The remaining gap is that it never says how a negative result manifests to the caller. That matters for a pre-flight check, but it's a modest omission.

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 no parameters, and the description correctly spends no space on argument semantics. The empty schema and 100% coverage mean there is nothing further to document.

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 gives a specific verb and resource: it inspects the host's network environment and names the fields it checks (SSID, Gateway). It implicitly distinguishes itself from siblings like router_get_status by scoping the check to the local host rather than the router itself, though it never names that sibling explicitly.

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 states a clear usage context: call this before applying configuration changes, and it names the failure conditions to watch for (University Wi-Fi such as SLIIT, mobile hotspot). It doesn't point to an alternative tool for the case where the check fails, so it stops just short of full when/when-not guidance.

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