hamravesh_list_databases

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'list,' implying a read operation, but does not confirm idempotency, permissions needed, rate limits, or any side effects. The description adds minimal transparency beyond the basic function.

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 sentence, concise and front-loaded. Every word is meaningful; there is no redundancy or unnecessary detail. It efficiently communicates the core 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 the low complexity (1 optional parameter, no output schema), the description minimally covers the basic purpose. However, it lacks explanation of the parameter and does not specify what information is returned. It is adequate but could be more complete.

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 optional parameter 'org' with no description in the schema (0% coverage). The tool description does not explain what 'org' represents (e.g., organization ID or name) or how it affects results. This is a critical gap for correct parameter usage.

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 states 'List of managed databases (DBaaS) of an organization,' which clearly identifies the tool's purpose (listing databases) and scope (per organization). However, it lacks an explicit verb like 'list' or 'retrieve,' though it is implied. There are no sibling tools with similar names, so distinction is not an issue.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or constraints. Sibling tools are for different resources (apps, keys), so confusion is low, but guidance is still absent.

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