status

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

Annotations already establish read-only and non-open-world behavior, and the description adds useful context that it reports database, role, profile, limits, and says what to fix on connection issues. It does not detail the exact response shape or troubleshooting scope, but it adds meaningful behavioral guidance beyond the annotations.

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 two short sentences with no wasted text. The initial-call guidance and connection-failure use case are front-loaded and easy to scan.

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 zero-parameter status tool with annotations and no output schema, the description is complete enough: it says what information is returned and when to invoke it. No additional schema or parameter explanation is needed.

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 tool has zero parameters, so there is no parameter semantics to explain. The schema is fully documented and the description appropriately does not spend space on nonexistent inputs.

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 identifies this as a read-only server-status tool that reports database, role, profile, and limit information. It distinguishes itself from schema-oriented siblings by framing its role as the first call and as a connection-problem diagnostic, though it lacks an explicit verb like "return" or "get."

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 gives explicit usage guidance: call it first, and call it when another tool reports a connection problem. These are the key moments an agent needs to select this tool, and no alternative tool is appropriate for this diagnostic role.

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