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

Annotations already cover the read-only, non-destructive, closed-world profile, so the bar is lower; the description adds the key behavioral fact that credentials are deliberately excluded and where they live instead, which prevents an agent from hunting for secrets via this tool. It doesn't mention pagination or response shape, but for a single-object read that is minor.

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 tight sentences, front-loaded with what is returned; the credential caveat and the sibling redirect each earn their place with no filler.

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 carries the return-value burden and does so by naming the fields returned, plus it clarifies the credential boundary and the alternative tool. The only missing piece is how/where to source the managedDatabaseId.

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?

Only one required parameter (managedDatabaseId) with 0% schema description coverage, so the schema adds nothing. The description supplies no information about where to obtain the ID or its expected format (e.g., from nexusai_managed_db_list), leaving a real gap even if the parameter is largely self-evident.

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 ('Return non-secret database metadata') and enumerates the fields returned (engine, status, host, port, database name), which also corrects the potentially misleading tool name 'connection'. It names nexusai_managed_db_attach as the contrasting operation, though it doesn't differentiate itself from siblings like nexusai_managed_db_list that likely also surface database info.

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?

Gives clear context for when to use this tool (fetch non-secret DB metadata) and explicitly redirects to nexusai_managed_db_attach for configuring an app server-side, plus points to the dashboard for credentials. It lacks any explicit exclusion relative to other read siblings such as nexusai_managed_db_list.

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