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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description only needs to add context. It does: it discloses the meaningful limitation that renames are only detected when sourceable, and clarifies what 'changed' means (range, values, default). It stops short of describing result shape or ordering.

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 that names the resource first and then enumerates the diff categories. No filler, no restatement of the title.

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 read-only, closed-world lookup with fully documented parameters and no output schema, the description covers what is compared and the key limitation on rename detection. The only gap is the shape of the returned diff (grouped settings vs. flat list), which an agent must discover by calling.

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 100%, so the schema already carries the parameter meaning. The description only implies the from/to relationship by saying 'between two releases' and adds nothing about version format or firmware selection beyond what the enum and defaults already state.

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 operation (diff CLI settings between two releases) and enumerates exactly what dimensions are compared (added, removed, renamed, changed). The resource and scope are unmistakable. It doesn't name a sibling alternative, but the diff framing is distinct enough from fw_check_cli and fw_param.

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?

Usage is only implied: an agent must infer that this is the right tool when comparing two firmware releases rather than validating a single CLI paste (fw_check_cli) or looking up one parameter (fw_param). No explicit when-to-use/when-not guidance is offered.

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