get_warehouse_settings

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

No annotations provided, so the description carries full burden. It discloses that the tool reads from `sys.databases` and returns settings, implying a read-only operation. It does not explicitly state 'read-only' or mention permissions, but the list of returned fields adds transparency.

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 well-structured, using a brief introductory sentence, a bulleted list of returned settings, and an Args section. Every sentence adds value with 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?

Given the tool has 2 parameters and an output schema exists (though not detailed in context), the description explains the return data (specific settings), the system table queried, and supported objects. This is sufficient for an agent to correctly invoke the tool.

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?

Input schema has 0% description coverage for parameters. The description adds value by defining each parameter: 'workspace: Workspace name or GUID' and 'item: Warehouse or SQL Analytics Endpoint name or GUID', which is not present in the 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 it returns server-side database settings for a warehouse, enumerates specific settings (result_set_caching, time_travel_retention_days, etc.), and explicitly mentions support for both Data Warehouses and SQL Analytics Endpoints, distinguishing it from sibling tools.

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 usage for reading warehouse settings, and siblings include set_* tools for modifications, so when to use is clear. However, it does not explicitly state when not to use or provide direct alternatives, but the context is sufficient.

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