get_sql_endpoint_permissions

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

With no annotations, the description carries the full burden. It correctly identifies the operation as read-only (returning data) and specifies the required role, but does not disclose additional behavioral aspects such as response format, pagination, or potential errors. The link provides external details but the description itself lacks depth.

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 brief at two sentences, with no extraneous content. All information is front-loaded. However, the link could be integrated more seamlessly, and the parameter documentation gap reduces overall efficiency.

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's simplicity (2 parameters, read-only), the description covers purpose and a key requirement. However, it omits parameter descriptions and sibling differentiation. The presence of an output schema mitigates some completeness need, but the parameter gap is notable.

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 0% description coverage, yet the description provides no explanation of the two required parameters ('workspace' and 'sql_endpoint'). It does not define their expected format, source, or relation to the endpoint, leaving the agent without guidance beyond parameter names.

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 'principals with access to a SQL Analytics Endpoint item.' It distinguishes from siblings like get_sql_endpoint (which likely returns endpoint details) and get_warehouse_permissions, making the tool's specific purpose unambiguous.

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 (Fabric Administrator role) but provides no explicit guidance on when to use this tool versus alternatives like get_warehouse_permissions. It implies usage context but lacks when-not or alternative comparisons.

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