get_warehouse_settings

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

No annotations are provided, so the description carries full burden. It indicates a read operation ('reads from sys.databases') and lists returned fields, but lacks details on auth requirements, rate limits, or error conditions. Adequate for a simple retrieval but not exhaustive.

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 with 4 sentences plus a structured Args section. Every sentence adds value: purpose, fields, supported resources, and parameter definitions. No redundancy.

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 tool with an output schema (not shown), the description is sufficiently complete. It specifies input parameters and returned fields. It could mention error handling or prerequisite existence checks, but the current detail is adequate.

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 has 2 parameters with only titles; the description adds meaning by specifying 'Workspace name or GUID' and 'Warehouse or SQL Analytics Endpoint name or GUID'. This clarifies usage beyond the schema's minimal information.

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 verb 'Return' and the resource 'current server-side database settings for a warehouse', and lists specific fields retrieved. It distinguishes from siblings like get_warehouse (general info) and get_warehouse_permissions.

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 notes that both Data Warehouses and SQL Analytics Endpoints are supported, providing clear usage context. It does not explicitly state when not to use or mention alternatives, but the sibling list implies differentiation.

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