LinkIt SQL: explore

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

Annotations already declare readOnlyHint=true, so the description does not need to restate it. The description adds valuable context: paginated, capped results safe for large catalogs, and details per action (e.g., table_info returns columns/keys/FKs/rowcount). This goes beyond the annotation without contradiction.

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?

A single sentence with the main purpose front-loaded, followed by a compact list of all actions. No redundant words; the structure efficiently communicates scope and behavior.

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 covers all actions and key behavioral traits (pagination, capping), but it does not explicitly address usage guidelines or explain pagination parameters (page, pageSize), though those are in the schema. For a discovery tool with this complexity, it is fairly complete.

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 100%, so all parameters are already documented. The description does not add parameter-specific semantics beyond the schema; it only provides high-level action context. Baseline 3 is appropriate given the high schema coverage.

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 discovers database objects and enumerates all nine actions (list_databases, list_tables, etc.). It is specific and easily distinguishes itself from query and system, which are for executing queries and system info.

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 implies this tool is for discovery but does not explicitly state when to use it over siblings (query, system) or when not to use it. No alternatives or exclusions are mentioned, leaving the agent to infer from context.

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