linode_list_databases

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

Annotations already declare readOnlyHint=true, so the description's addition that the 'root password is never returned' provides useful behavioral context. However, it does not elaborate on other behaviors like pagination or error conditions.

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?

Two concise sentences with critical information front-loaded. No superfluous words; each sentence adds value. The structure is ideal for quick comprehension.

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 covers the tool's purpose, scope, and a key behavioral note (password exclusion). The output schema likely documents return structure, but the missing parameter explanation slightly reduces completeness. Overall, adequate for a simple list operation.

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 single parameter 'detail' is not mentioned in the description. With 0% schema description coverage, the description should explain the parameter's effect (e.g., controlling field verbosity). This omission leaves the agent unsure of how to use the parameter.

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 explicitly states the verb 'List', the resource 'Managed Database clusters', the scope 'in the account (all engines)', and lists specific fields returned. This clearly distinguishes it from sibling list tools like linode_list_database_engines and linode_list_database_types.

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 usage for listing all database clusters but does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites, filtering, or when not to use it.

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