apply_connection_convention

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It does reveal that the tool mutates tags and metadata and derives display identity from native end_user, but it does not disclose whether existing tags/metadata are overwritten or merged, whether patchMetadata affects this, what permissions are needed, or whether the operation is reversible or idempotent.

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 economical sentence with no fluff and the core phrase 'Apply suggested tags and metadata' is front-loaded. However, for an eight-parameter mutation tool, the terseness becomes under-specification rather than effective conciseness, leaving too much unsaid.

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?

With eight parameters, no annotations, and only a short description, the tool is not contextually complete. It does not explain what a 'convention' is in this domain, how required parameters relate to behavior, what happens to existing tags/metadata, or how patchMetadata and oauthAppOwner factor in. The output schema is present, so return values need not be described, but the operational context is still critically incomplete.

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%, so the description must compensate for eight undocumented parameters. It only gestures at one concept ('native end_user' possibly mapping to principal) and vague 'tags and metadata', but does not explain environment, connectionId, providerConfigKey, ownerKind, purpose, oauthAppOwner, or patchMetadata. This is inadequate for a tool with six required parameters.

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 specific action ('Apply'), a resource ('suggested tags and metadata'), and an additional behavior ('deriving display identity from native end_user'). This distinguishes it from sibling tools like replace_connection_tags, update_connection_metadata, and build_connection_convention, since it combines these concerns and explicitly mentions identity derivation.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention describe_connection_convention, build_connection_convention, replace_connection_tags, or update_connection_metadata, nor does it state conditions or exclusions. The usage context must be inferred entirely from the name and description.

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