db_status

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

The description discloses that a live SELECT 1 is performed (not just cached info) and clarifies that providing a profile does not alter the sticky session. This gives full transparency about side effects and behavior, especially given no annotations are present.

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 concise, using two short sentences to convey purpose, optional argument, and side-effect behavior. No unnecessary words or repetition.

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?

The description explicitly lists the output content (profile, host, database, write mode, health check result), making it clear what the tool returns even without an output schema. The context is complete for a status/health check tool.

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?

Both parameters are fully described in the schema with clear meanings: profile for connection profile (with sticky session context) and database as an optional override. The descriptions are sufficient and match the schema coverage of 100%.

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 clearly states the tool's purpose: to show current sticky PostgreSQL profile, host, database, write mode, and perform a live SELECT 1 health check. It is specific and distinguishes itself from sibling tools like db_query or db_list_databases.

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?

It explains the optional profile argument for a one-shot check without changing the sticky session, implying usage for verifying current state. However, it does not explicitly state when to prefer this over alternatives, though the context is clear from sibling tools.

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