get_database

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about read-only semantics, required permissions, error behavior, or return shape. For a lookup tool with zero structured hints, this is a complete gap.

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?

It is a single short phrase, so it is not bloated, but the brevity reflects under-specification rather than disciplined conciseness. There is no structure or front-loaded useful content to credit.

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 two-parameter, fully-required tool with no annotations, no output schema, and 0% parameter documentation, the description supplies none of the missing context. It is inadequate for correct invocation.

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 both required parameters (id, type) are undocumented in the schema. The description does not mention either parameter, so an agent has no idea what "type" enumerates or what "id" refers to.

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?

"Get database details" essentially restates the tool name get_database with the vague word "details" as the only addition. It does not say which database fields are returned or how it differs from the sibling list_databases, so an agent gains no real selection signal.

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 when-to-use, when-not-to-use, or alternative guidance. Siblings such as list_databases and get_system_info exist, and the agent is given nothing to decide between them.

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