Check Update

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

It explicitly discloses the key side-effect boundary: it does NOT install anything)Skip. It also hints at network dependency with 'latest PyPI version (if reachable)', though it does not detail failure modes or exit behavior. Good coverage for such a simple 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?

Two short, front-loaded sentences with clear formatting. The core purpose appears first, followed by the side-effect warning and the alternative tool. No wasted words.

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 simple check tool, the description covers purpose, output, network dependency, and the related upgrade action. Everything an agent needs to decide whether to invoke this tool is present.

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 schema fully describes the only parameter, lang, with a default and description. The tool description does not add significant additional meaning about parameters, so it does not exceed the baseline.

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 uses a specific verb ('compare') and a clear resource ('installed fcop-mcp version' vs 'latest on PyPI'). It also distinguishes itself from the sibling upgrade_fcop by explicitly stating it does not install.

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?

The description clearly states what this tool does and explicitly says it does not install anything, directing agents to call upgrade_fcop instead. This provides a clear when-to-use / when-not-to-use boundary.

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