update_connection

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

With no annotations, the description carries the full burden. It discloses that this is a mutation and usefully enumerates the mutable fields (host, login, password, schema, port, extra), plus adds security guidance about pulling credentials from a secret store — genuine value beyond the schema. However, it never says whether the update is partial/merge or full replacement, what happens to omitted fields, or what permissions are required, which are the critical unknowns for a write operation on a nested-object payload.

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 purpose statement is front-loaded in a single sentence, followed by a compact Args block with one line per parameter. The docstring-style formatting is slightly heavier than free prose but nothing is redundant.

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?

An output schema exists, so return values need not be explained. But for a two-parameter, nested-object mutation tool with zero annotations and zero schema coverage, the description leaves out update semantics (partial vs. replace), permission requirements, and error behavior when connection_id does not exist — all of which an agent would want before invoking.

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, and it partially does: connection_id is defined as the "Exact Airflow connection identifier" and connection_data is described as a JSON body with example fields. The field list is explicitly non-exhaustive ("such as") and the schema allows additionalProperties, so the agent still cannot know the full acceptable payload shape or the format of nested values like extra.

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?

States a specific verb and resource ("Updates an existing connection") and the word "existing" implicitly separates it from the create_connection sibling. It does not explicitly name the alternatives (create_connection, delete_connection, get_connection), so differentiation is inferable rather than stated.

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?

Usage is only implied by "existing" — an agent can reason that this is for modifying a connection that already exists rather than creating one, but no explicit when-to-use/when-not rule or prerequisite (e.g., the connection must already exist) is given. The credential-sourcing instruction is the only concrete guidance offered.

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