Checks if a newer version of the Suite is available on PyPI or GitHub and provides the update instruction or command.
Comprueba si existe una versión más reciente de la Suite en PyPI o GitHub e informa la instrucción en lenguaje natural o comando para actualizarla.
| Name | Required | Description | Default |
|---|---|---|---|
| forzar | No | Si es True, ignora la caché local de 24 horas y consulta en vivo |
Changes observed during successful MCP inspections.
v1.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It does disclose external network sources (PyPI and GitHub) and roughly what it returns, which is useful, but it omits that results are normally served from a 24-hour local cache, that no authentication is needed, and whether the call is safe/read-only.
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 sentence with no filler, front-loading the check action and then the reported output. Nothing is wasted and nothing essential is buried.
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 no output schema and no annotations, the description adequately covers what is checked and what is reported. It stops short of the sibling relationship (check vs. auto-update) and the caching/network behavior an agent may need to reason about latency or repeat calls.
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% and the single parameter 'forzar' is fully documented in the schema. The description adds no syntax, default, or behavioral nuance beyond what the schema already states, so the baseline of 3 applies.
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?
Specific verb ('Comprueba si existe una versión más reciente') plus resource (the Suite on PyPI/GitHub), and it states the outcome the agent gets back (an update instruction or command). It does not name or contrast with its sibling suite_auto_update, so the agent must infer which one to call from the verb 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?
The description implies a pre-update check but never states when to use this instead of suite_auto_update, nor any preconditions. No exclusions, no alternatives, no guidance about acting on the result.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.