get_connection

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

No annotations are provided, so the description carries full burden. It discloses that 'credential-like response fields are redacted', which is a useful behavioral trait. However, it does not mention other behaviors like read-only nature (though 'Get' implies it), rate limits, or authentication needs.

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 very concise (one sentence) but at the cost of omitting necessary details like parameter meanings or output structure. It is not overly verbose but lacks completeness.

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 4 parameters (3 required), no output schema, and no annotations, the description is insufficient. It doesn't explain the purpose of the connection, the context of Nango, or what the response contains beyond the redaction note. The agent likely lacks enough context to use the tool correctly.

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% and the tool description does not explain any parameters. Neither 'environment', 'connection_id', 'provider_config_key', nor 'include_credentials' are described. The description adds no meaning beyond the schema's type and name information.

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?

Description clearly states 'Get a Nango connection', using a specific verb and resource. It distinguishes from sibling tools like 'list_connections' (which lists) and 'get_connection_context' (which gets context). However, it lacks explicit mention of retrieving by identifiers, which could be inferred from required parameters.

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 on when to use this tool versus alternatives like 'list_connections' or 'get_connection_context'. Also no indication of prerequisites (e.g., environment must exist) or typical use cases.

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