get_connection

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

No annotations exist. The description is too brief to disclose behavioral traits such as whether the operation is read-only, requires specific permissions, or has side effects. It adds no context beyond the basic action.

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?

A single, well-structured sentence conveys the essential purpose without extraneous words. It is optimized for quick understanding.

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 has an output schema that likely documents return structure, the description is largely sufficient for a simple fetch-by-ID operation. Some might desire mention of typical usage context (e.g., to retrieve details before updating), but the gap is minor.

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 clarifies that the required 'object_id' is a numeric ID, adding meaning beyond the schema (which only specifies integer type without description). With 0% schema description coverage, this is a minor but useful addition.

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 action ('Get'), the resource ('single CDV data connection'), and the method ('by its numeric ID'). It effectively distinguishes from siblings like list_connections (list all) and create/update/delete operations.

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 guidance provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or when to choose other tools like get_dataset or list_connections.

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