router_firmware

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the notable behavioral fact that the result includes a verification status, but it never explains what 'verified against it' means, who performs that verification, or what a negative result implies — a meaningful gap for a compatibility-oriented tool.

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 compact sentence with no filler, front-loading the returned fields. It is slightly elliptical — the pronoun 'it' and the missing verb force a small amount of interpretation.

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?

An output schema exists, so return values need not be spelled out, and the tool is structurally simple with zero parameters. Still, for a tool whose whole purpose is a compatibility verdict, the description leaves the agent without enough context to interpret or act on that verdict.

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 has nothing to disambiguate, so the baseline of 4 applies. No parameter-level meaning is added or needed.

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 and scope: firmware version, firmware date, and a verification flag. It lacks an explicit verb and does not distinguish itself from nearby read tools such as router_status or router_diagnostics, so an agent can infer the resource but not the boundary from the text alone.

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 statement of when to call this versus router_status, router_diagnostics, or get_policy, and no prerequisites or exclusions. The agent must guess that this is the compatibility-check tool rather than a general status tool.

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