get_tableau_connection_info

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

No annotations exist, so the description carries full burden. It only states it returns a URL, with no mention of side effects, permissions, or limitations. Since the tool is a simple read-only operation, this is adequate but not thorough.

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 extremely concise, one sentence plus a list of example queries. Every word serves a purpose, and the structure is front-loaded with the key action.

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 an output schema exists, explanation of return values is unnecessary. However, the missing parameter description and lack of behavioral context make it only partially complete. For a simple tool, it suffices but has clear gaps.

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 schema description coverage is 0%, yet the description does not explain the 'port' parameter or its effect on the URL. The parameter exists with a default, but its purpose is unclear, leaving the agent without guidance.

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 the Tableau Web Data Connector URL for connecting Tableau Desktop to nable. This is a specific verb and resource, and no sibling tool covers Tableau integration, so it is well-distinguished.

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 lists explicit example queries (e.g., 'How do I connect Tableau?'), indicating when to use the tool. However, it does not provide exclusions or mention alternative tools, which would be helpful but not critical given the tool's uniqueness.

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