list_schemas

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

Discloses the operation is read-only and covers both endpoints. Explains which schemas are excluded (system schemas) and that dbo is included, offering behavioral insight beyond the basic action.

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?

Extremely concise: a single paragraph that front-loads the main purpose, then adds exclusions and args. Every sentence is essential, 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?

Covers all necessary context for a list tool: scope, exclusions, compatibility, and parameter descriptions. Output schema is present, so return values need not be described. Complete for the task.

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?

Compensates for zero schema coverage by describing each parameter (workspace and item) with name format guidance (name or GUID). Adds meaning beyond the bare property definitions.

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 the tool lists user-defined SQL schemas, distinguishing it from other schema operations. Specifies exclusions and inclusions, leaving no ambiguity about the resource and action.

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?

Provides context on when to use (listing schemas) and that it works on both warehouse and SQL Analytics Endpoints. Does not explicitly contrast with siblings like create_schema or delete_schema, but the purpose is clear enough.

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