cloud_list_database_tokens

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

With no annotations, the description carries the burden of disclosing behavior. It clearly indicates a read-only listing operation and mentions returned fields (permissions, creation dates), but omits authentication requirements, error conditions, or scope limitations. Adequate but minimal.

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 concise, two sentences, and front-loaded with the action ('List all database tokens'). It adds no 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?

The description states the tool's scope and key return fields, which is good for a simple list tool. It could mention pagination or boundaries of 'all', but the core functionality is covered adequately.

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 tool has zero parameters, so parameter semantics are not applicable. The description clarifies what the tool lists and returns, which is sufficient given the parameterless schema.

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 tool lists database tokens for InfluxDB Cloud-Dedicated/Clustered clusters, specifying the resource (database tokens) and scope. It distinguishes itself from sibling tools like list_admin_tokens by focusing on database tokens.

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 provides context (targets cloud-dedicated/clustered clusters) but does not explicitly mention when to use this tool versus alternatives like list_admin_tokens or list_resource_tokens. The name implies usage, but no direct guidance is given.

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