superset_database_get

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

No annotations are provided, so the description must carry the burden of disclosing behavior. The verb 'Get' implies a read-only operation, which is useful. However, it does not mention authentication requirements, error handling (e.g., invalid ID), or any side effects. The description is not misleading but is minimal.

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 and front-loaded, stating the purpose in the first sentence. The IMPORTANT note is relevant and the Args section is clearly formatted. Every line earns its place with no 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 getter with one parameter, the description covers the purpose, prerequisite, and parameter meaning. The output schema exists, so return values need not be described. It could mention what happens if the ID is not found, but overall it is adequate for the tool's complexity.

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 schema only defines 'database_id' as an integer, but the description adds valuable context: 'Connection ID (integer from database_list result).' This tells the agent where to obtain the ID and reinforces its type, going beyond the raw schema.

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 function: 'Get detailed information about a database connection by ID.' This uses a specific verb ('Get'), identifies the resource ('database connection'), and specifies the scope ('by ID'). It also implicitly distinguishes from the list sibling by requiring a known ID.

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 description provides explicit usage guidance: 'IMPORTANT: if the ID is unknown, call superset_database_list first.' This tells the agent when to use this tool vs. an alternative (list). It does not mention when not to use it or other alternatives like connection_info, but the core context is clear.

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