set_hyper_connection

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

No annotations provided, so description carries full burden. It states the tool configures a connection but does not disclose if it modifies the workbook in-place, requires a specific state, or has side effects (e.g., closing existing connections). No mention of permissions or response behavior.

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?

Single sentence, no wasted words. Front-loads the main purpose. Perfectly concise for a simple tool.

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 3 parameters (1 required), no annotations, and an output schema (but description doesn't reference it), the description is incomplete. It doesn't explain what the output schema represents or how the parameters interact. Sibling tools suggest a data source context, but more detail is needed for effective use.

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 description coverage is 0%, so description must compensate. It does not describe any parameter semantics (filepath, table_name, tables) beyond their schema titles. Baseline 3 is appropriate since no param info is added, but coverage is low.

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 tool configures a workbook datasource to use a local Hyper extract connection. The verb 'Configure' and resource 'workbook datasource' are specific, and it distinguishes from sibling tools like set_excel_connection or set_mysql_connection by specifying 'Hyper extract'.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., set_excel_connection, set_mysql_connection). It does not mention prerequisites or when not to use it. The context of using a local Hyper extract is implied but not elaborated.

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