describe_connection_convention

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'explain', which implies a read-only operation, but it does not state whether this is purely informational, whether it performs any side effects, or what the return format is. The lack of behavioral detail is a significant gap for a tool that generates output.

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 a single sentence, but it is under-specified rather than concise. It omits critical information about the tool's purpose and behavior, so brevity here does not equate to efficiency—it is a deficiency.

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?

Despite having an output schema, the description does not explain what the tool returns or how the output relates to the 'helpers' it describes. It does not provide enough context for an agent to know what kind of response to expect or how to integrate this tool into a workflow, especially given the rich sibling toolset.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and no ambiguity exists in the schema.

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 states a verb ('Explain') and a resource ('Nango MCP connection convention helpers'), but the resource is vague—'helpers' is ambiguous and does not clarify what these are. It does not distinguish this from sibling tools like build_connection_convention or apply_connection_convention, leaving an agent uncertain about the exact scope of the explanation.

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 is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions. An agent cannot infer when 'describing' is more appropriate than 'auditing', 'building', or 'applying' conventions.

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