list_database_services

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

With zero annotations, the description must disclose behavioral traits. It only states 'list' without mentioning safety (read-only), pagination behavior, authentication needs, or rate limits. The agent gets no insight into side effects or performance implications.

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 only three words, which is concise but at the expense of valuable information. It lacks structure and should include parameter hints or filtering details. Being too short reduces usefulness.

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 tool has four parameters, no output schema, and many siblings, the description is severely incomplete. It fails to explain pagination, default values, filter options, or return format. The agent cannot determine how to correctly invoke the tool from this description alone.

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 description coverage is 0%, and the description offers no explanation for any of the four parameters (limit, offset, fields, include_deleted). The agent must rely solely on parameter names, which may be ambiguous (e.g., 'fields' without format).

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 database services' clearly states the verb (list) and resource (database services). However, it does not differentiate from many sibling list tools like list_databases or list_dashboard_services, leaving ambiguity about what a 'database service' constitutes.

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?

There is no guidance on when to use this tool versus alternatives. No mention of typical use cases, prerequisites, or whether this is a listing of all services or filtered by some context. The absence of any usage context leaves the agent to infer.

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