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

Annotations already declare destructive=true and openWorld=true, and the description adds meaningful scope: this upgrades the LMCP app itself and does not edit user data. It also implies normal installs may involve download and restart, though it does not spell out downtime, permissions, or recovery 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?

Two tightly written sentences, front-loaded with the main purpose and followed by the key mode modifier. There is no redundant or wasted text.

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 annotations covering destructive/openWorld behavior and an output schema present, the description provides enough context to choose and invoke the tool correctly. It could still be stronger by explicitly noting restart/downtime implications for a normal install.

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 both parameters are already documented. The description reinforces check_only semantics but does not add much beyond the schema, and it does not mention that confirm is ignored.

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 states a specific action and resource: checking for and installing a newer LMCP version, scoped as a self-upgrade of the app rather than data editing. It is clear, but it does not explicitly distinguish this tool from nearby siblings such as lmcp_upgrade_diagnostics or lmcp_doctor.

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 useful mode guidance by saying check_only=true performs a report-only check with no download or restart. However, it does not state when to use this versus diagnostic/upgrade-adjacent siblings, nor does it describe prerequisites or when not to use it.

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