get_warehouse_permissions

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only mentions the admin role requirement but fails to disclose side effects, idempotency, rate limits, or whether any data is modified.

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 three short sentences. The first sentence clearly states the purpose, front-loading the most important information. Every sentence adds value without 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?

The tool has an output schema, so the description does not need to explain return values. However, it lacks context on how to interpret the returned principals (e.g., user vs. group, format) and does not mention any error conditions or edge cases.

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 input schema has two parameters (workspace and warehouse) with no descriptions. Schema description coverage is 0%, and the description does not add any semantics about what these parameters represent or how they should be formatted.

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 states the verb 'Return' and the resource 'principals with access to a Warehouse item', making the purpose clear. However, it does not differentiate from sibling tools like get_sql_endpoint_permissions, which also return 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 mentions a prerequisite (requires Fabric Administrator role) but does not provide guidance on when to use this tool versus alternatives, such as when to use get_warehouse_permissions vs. get_sql_endpoint_permissions.

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