list_user_dbs

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

No annotations are provided, so the description carries the burden. It transparently states the tool lists user databases in the account, but it does not disclose pagination behavior despite the limit/offset parameters, which could make 'all' potentially misleading given the max 100 limit.

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 that front-loads the verb and resource. It contains no fluff or redundant wording, earning every word.

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?

For a simple list tool, the description and schema are mostly sufficient. However, there is no output schema and the description does not clarify pagination or return shape, leaving minor gaps in completeness.

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 schema already provides full descriptions for limit and offset (100% coverage). The description adds no additional parameter semantics, so a baseline score of 3 is appropriate.

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 'List all user databases in your AdButler account' uses a specific verb ('List'), specifies the resource ('user databases'), and scopes it to the account. It clearly distinguishes itself from sibling tools like get_user_db and create_user_db by indicating a collection-listing operation.

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 its use case by stating it lists all user databases, so an agent can infer when to call it. However, it provides no explicit guidance on when to use it versus alternatives (e.g., get_user_db for a single database) or any exclusions.

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