save_vps

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

Discloses that credentials are saved encrypted in ~/.mt5-reader/vps.json and that after call, re-entry is never needed. Provides valuable behavioral context beyond schema, though could mention overwrite 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 sentences, no wasted words, front-loaded with key verb and resource.

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?

Given high schema coverage and output schema existence, description covers purpose, persistence, and encryption. Minor gap: no mention of update overwrite behavior.

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 coverage is 100%, so baseline 3. Description does not add parameter-level meaning beyond listing the four fields.

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?

Description clearly states verb 'aggiunge o aggiorna' (adds or updates) and resource 'VPS nella rubrica locale sicura'. Distinguishes from siblings like list_vps and delete_vps.

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?

Implies usage for storing or updating VPS credentials, but does not explicitly compare with connect_vps or other operations. Lack of when-not-to-use guidance.

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