apply_connection_convention

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

The description implies a mutation operation ('apply') but does not disclose side effects such as whether existing tags are overwritten, whether the action is reversible, or if authentication privileges are needed. No annotations are provided, so the description carries the full burden, which it fails to meet.

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 omits critical details, making it under-specified rather than appropriately concise. It does not earn its place because it fails to add value beyond the tool name.

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 complexity of 9 parameters (6 required), no annotations, and no output schema details, the description is woefully incomplete. It does not explain the confirmation workflow, metadata patching behavior, or the implications of the 'owner_kind' and 'purpose' fields.

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?

With 0% schema description coverage and 9 parameters (6 required), the description adds no meaning beyond 'tags and metadata.' It does not explain the purpose of any parameter such as 'confirmation', 'patch_metadata', or 'principal', leaving the agent unable to determine proper values without external knowledge.

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 the verb 'apply' and the resource 'suggested Nango MCP tags and metadata to an existing connection,' which clearly indicates the tool's purpose. It distinguishes from siblings like 'build_connection_convention' (which creates conventions) and 'describe_connection_convention' (which reads). However, it does not explicitly differentiate from 'patch_connection_tags' which might have overlapping functionality.

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?

There is no guidance on when to use this tool versus alternatives like 'audit_connection_conventions' or 'build_connection_convention'. The description does not mention prerequisites, required permissions, or context for use, leaving the agent to infer usage without explicit guidance.

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