db_get_user

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

With no annotations, the description carries the full disclosure burden. 'Get information' clearly signals a read-only operation and the Returns line indicates the expected output. However, it does not mention error behavior, permission requirements, or side-effect absence; acceptable for a simple getter but not rich disclosure.

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 compact, front-loaded with the core purpose, and uses clear Args/Returns sections. Every sentence earns its place without redundancy or fluff.

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 simple read operation with an output schema present and only two parameters, the description covers the essential semantics. It explains what the tool returns, including permissions. Minor gaps are the lack of explicit alternative routing and behavioral caveats, but these do not seriously hinder 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%, so the description must add meaning to the bare parameter names. It does: database_id is explained as 'database ID or label' and username as 'the username to get information for.' This goes beyond the schema by clarifying the database_id format flexibility.

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 states a specific verb and resource: 'Get information about a specific database user.' The qualifier 'specific' distinguishes it from listing tools like db_list_users, and the parameter names make the target unambiguous.

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?

The phrase 'specific database user' implies this is for singular lookups rather than listing all users, but the description does not explicitly mention when to use it versus alternatives such as db_list_users or db_get_logical_database. Usage context is implied rather than stated.

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