apply_connection_convention

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states that it applies tags and metadata but does not disclose side effects: whether it overwrites existing tags/metadata, whether it is idempotent, if it requires specific permissions, or what the output will be. The mutation nature is implied but not elaborated, leaving an agent uncertain about consequences.

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 concise sentence that front-loads the action and target. There is no unnecessary verbosity or filler. However, it is so brief that it sacrifices clarity and completeness; the conciseness is effective but not balanced with needed detail.

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's complexity (10 parameters, 6 required, no schema descriptions, and no annotations), the description is severely incomplete. It does not explain what 'suggested tags' are, how they are generated, what input parameters are expected, what the output schema represents, or any preconditions. The description fails to equip an agent to correctly call this tool.

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 input schema has 10 parameters with no descriptions (coverage 0%), and the tool description adds zero meaning to them. It does not explain fields like principal, owner_kind, purpose, patch_metadata, or oauth_app_owner. Since the description is the only source of semantics and it fails to define any parameter, the agent cannot infer what values to supply. This is a critical gap at 0% coverage.

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 uses a specific verb 'Apply' with a clear resource: 'suggested Nango MCP tags and metadata to an existing connection'. It distinguishes the action from siblings like build_connection_convention (which likely constructs a convention) and describe_connection_convention (which describes it). The intended operation is unambiguous, though 'suggested' is somewhat vague.

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 given on when to use this tool versus alternatives like set_connection_metadata or patch_connection_tags. The description does not state prerequisites, such as whether a connection convention must be built first, or when to prefer this over directly setting metadata/tags. The intended context is only implied by the word 'suggested'.

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