deployado_get_database

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

Annotations already declare readOnlyHint/idempotentHint, so safety is covered; the description adds the meaningful behavioral fact that the response exposes connection credentials — a sensitive-data disclosure an agent should know before echoing output. It stops short of saying whether credentials are long-lived or secrets should be handled carefully.

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?

One front-loaded sentence that states the resource and the most important content of the response. No filler, though slightly terse given the sensitivity of the returned data.

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, the description must carry return-shape information; it only lists 'connection URL and credentials' without indicating what other fields come back (host, port, name, engine) or the credential structure. Adequate to call correctly, but thin for interpreting the result.

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 100% ('Database ID (UUID)'), so the schema fully documents the single parameter. The description adds nothing about identifier format or lookup behavior; baseline 3 applies.

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?

Names a specific verb ('Get detailed information') and resource ('a database'), and clarifies the payload (connection URL and credentials) so it is distinguishable from deployado_list_databases. It does not explicitly name siblings, but the single-resource fetch is clear.

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?

Usage is only implied: fetch details for one database by ID. There is no explicit guidance on when to call this versus deployado_list_databases or deployado_connect_database, nor any prerequisites or exclusions.

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