get_connection

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

With no annotations, the description carries the burden. 'Get' implies a read-only operation, and the return type is mentioned generically as 'Dict[str, Any]: Response data.' However, it does not disclose any side effects, permissions, or specifics about the response contents, leaving some ambiguity.

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 and structured with clear sections for a summary, args, and returns. Every line is necessary, and there is no redundant wording. It front-loads the primary purpose.

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?

For a simple one-parameter getter, the description is nearly complete. It covers the operation, parameter, and return type. However, the return value is vaguely described as 'Dict[str, Any]: Response data' and lacks specifics about the response fields, which would improve completeness.

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 description adds semantic meaning to the sole parameter by stating 'Required. Connection ID,' which compensates for the schema's 0% description coverage. It clarifies what the ID represents, though it could be more detailed (e.g., format or example).

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 a specific action: 'Get a connection by ID.' It specifies the resource (connection) and the scope (by ID), which distinguishes it from sibling tools like list_connections and update_connection. The verb 'Get' accurately conveys a read operation.

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 usage when a connection ID is available, but it does not explicitly state when to use this tool over alternatives or provide any exclusions. It lacks explicit guidance on when not to use it or how it relates to list_connections.

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