get_table_constraints

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

Discloses automatic uppercasing of table name and return format [{constraint, type, index}]. No annotation provided, so description compensates well. Could mention read-only nature, but not critical.

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?

Three concise sentences: purpose, parameter guidance, return format and alternative. Every sentence adds value; no wasted words.

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?

Complete for a simple read tool with no output schema. Explains return structure and points to get_foreign_keys for more detail. No missing critical information.

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?

With 0% schema coverage, the description fully explains both parameters: database from list_databases, table from list_objects with uppercase transformation. Adds essential context beyond bare 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?

Clearly states it returns all constraints (PRIMARY KEY, FOREIGN KEY, UNIQUE, CHECK) on a table. Distinguishes from sibling tool get_foreign_keys.

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?

Explicitly says when to use (get all constraints) and when not (use get_foreign_keys for full FK details). Provides parameter hints: database from list_databases, table from list_objects with uppercasing.

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