turso_get_database

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description adds essentially nothing about behavior. It does not mention that api_key/org/name must be supplied, whether a nonexistent database errors, or what detail set is returned (e.g. hostnames, groups, sizes).

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?

A single short sentence that is front-loaded with the verb and resource and contains no filler. It is concise to the point of under-specification, but there is no wasted text.

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 read-only lookup tool with three required parameters at 33% schema coverage and no output schema, the description should clarify the two undocumented parameters and the fact that the result is a single database object. It also never names the alternative listing tool, so the definition is incomplete for correct tool selection.

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 only 33% – 'org' and 'api_key' are completely undocumented in the schema and the description supplies no meaning for either. Only 'name' is covered ("Database name" in the schema), and the description contributes no additional parameter guidance such as org slug format or where the API key comes from.

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?

States a specific verb and resource (get details for a specific Turso database), which is enough to distinguish it from turso_create_database or turso_execute_sql by name alone. However, it never explicitly contrasts with turso_list_databases, the closest sibling, so the agent must infer the single-record vs. list distinction from the description names.

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 statement of when to use this instead of turso_list_databases (to enumerate databases) or turso_execute_sql, and no prerequisites such as needing an existing database created first. Usage is only implied by the tool name.

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