fabric_get_sql_endpoint

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

The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that the tool returns connection string and other info, which is consistent. No additional behavioral traits (e.g., pagination, rate limits) are disclosed, but the read-only nature is clear from annotations.

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 sentence with no extraneous words. It is front-loaded and efficient, earning its place.

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 is simple (2 params, no nested objects, no output schema). The description hints at the return value ('connection string, etc.'), which is adequate given the low complexity. It could be more precise about what 'etc.' includes, but overall it is sufficiently complete.

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%: both 'sqlEndpointId' and 'workspace' are described in the input schema. The description does not add further meaning beyond what the schema already provides, so it meets the baseline.

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 uses a specific verb 'Get' and resource 'SQL analytics endpoint', with a hint of the return value ('connection string, etc.'). It clearly distinguishes this from sibling tools like fabric_list_sql_endpoints (for listing) and fabric_refresh_sql_endpoint_metadata (for refreshing).

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 the tool is for retrieving details of a specific endpoint, but does not explicitly state when to use it versus alternatives like listing first or refreshing. It provides clear context but lacks explicit when-not recommendations.

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