ssh_db_query

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is read-only and accepts only SELECT queries (or MongoDB find), adding safety context. However, it does not mention authentication details, result handling, or potential limitations like timeout.

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?

The description is a single concise sentence of 10 words, front-loading the key constraints. No wasteful or redundant information.

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 full schema parameter coverage and moderate tool complexity, the description is largely adequate. It could be improved by mentioning output behavior (e.g., returns query results) or result limits, but it covers essential safety constraints.

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?

All 9 parameters have schema descriptions (100% coverage), earning a baseline of 3. The description adds value by clarifying that the 'query' parameter must be a SELECT or MongoDB find query, which is not explicit in the schema descriptions.

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 the action 'Execute SELECT query' and the resource 'database', with explicit read-only and SELECT-only constraints. It distinguishes itself from sibling tools like ssh_db_dump and ssh_db_import.

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 explicitly restricts usage to SELECT queries and read-only operations, which guides appropriate use. However, it does not provide explicit alternatives or when-not-to-use scenarios.

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