fabric_get_warehouse

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

The readOnlyHint annotation already indicates a safe read operation, so the description does not need to restate that. The mention of 'includes its SQL connection string' adds some behavioral context (e.g., possible sensitivity), but no warnings or details about authentication, rate limits, or other traits are provided.

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 a single, front-loaded sentence with zero wasted words. It efficiently conveys the purpose and a key return detail.

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-only get operation with no output schema, the description adequately covers the most relevant context (the connection string). It does not explain the full return object, but this is acceptable given the tool's simplicity and the annotation coverage.

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 coverage is 100% for both parameters (warehouseId and workspace). The description adds no additional meaning beyond the schema, such as clarifying the default value of workspace or the format of warehouseId. Baseline score of 3 is appropriate.

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 action 'Get a warehouse' and adds a key differentiator 'includes its SQL connection string', which distinguishes it from other get tools like fabric_get_lakehouse or fabric_get_eventhouse. However, it does not explicitly differentiate from fabric_get_item or fabric_get_sql_endpoint.

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 provides no guidance on when to use this tool versus its many siblings, such as fabric_list_warehouses (for listing) or fabric_get_sql_endpoint (for SQL endpoint details). No when-to-use or when-not-to-use instructions are given.

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