list_terminals

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

No annotations provided, so description carries full burden. It indicates a read operation (listing) and specifies output fields, but does not disclose any side effects, authentication requirements, rate limits, or error behavior. Adequate but not extensive.

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?

Three sentences, each adding value: the first states the action, the second specifies output, the third provides usage guidance. No unnecessary words; front-loaded with the main purpose.

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 it's a simple list tool with one required parameter, the description covers the output fields and usage guidance. It lacks mention of error handling (e.g., invalid VPS name), but overall it is fairly complete for the agent's needs.

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 input schema has one parameter 'vps' with a description. The tool description goes beyond the schema by referencing a sibling tool list_vps to discover valid VPS names, which helps the agent understand how to populate the parameter correctly.

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 clearly states it lists all active MT5 terminals on a VPS, and specifies the returned fields (name, login, broker, server, connection status). It implicitly distinguishes itself from siblings by advising to use this tool before others to discover terminal names.

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?

Explicitly says 'Usare sempre questo tool prima degli altri per scoprire i nomi dei terminali disponibili' (Use this tool before others to discover available terminal names), providing clear when-to-use context and implying not to use other tools first.

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