get_database

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

With no annotations provided, the description must disclose behavioral traits like idempotency (read-only), authentication requirements, or error handling. It only states the basic action, which is insufficient for an agent to understand the tool's behavior.

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 extremely concise (8 words) and front-loaded with the verb and resource. However, it may be too minimal to provide sufficient context; it earns its place but could include more value without becoming verbose.

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?

With no output schema and no annotations, the description should clarify what information is returned (e.g., full database object with settings, tables, etc.) and any prerequisites (e.g., database must exist). The current description only states the action, making it incomplete for safe agent usage.

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 parameter id is documented in the schema as 'Database ID', but the tool description does not elaborate on its meaning, format, or constraints. Given the 0% schema coverage metric, the description should compensate but fails to do so, leaving agents to rely on the schema alone.

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 uses the verb 'Get' and identifies the resource 'a single database' with method 'by ID'. It is clear and specific, but does not differentiate from sibling tools like get_database_metadata or list_databases, limiting its score to 4.

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 no guidance on when to use this tool versus alternatives such as list_databases or get_database_metadata. An agent could benefit from knowing that this tool returns the complete database object, while others return specific aspects.

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