set_connection_metadata

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action ('set or patch') without explaining side effects, whether it overwrites or merges, or what happens to existing metadata. No permissions or side effects are mentioned.

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?

A single concise sentence with the primary action front-loaded, followed by a useful caution. No wasted words, though it omits necessary 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?

For a mutation tool with 5 parameters and no output schema or annotations, the description is minimal. It does not explain the purpose of metadata, how it relates to connections, or what the expected outcome is. The missing behavioral and parameter details make this 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. It adds a semantic constraint on the metadata parameter (no credentials/config), but other parameters (environment, connection_id, provider_config_key, patch) are left entirely undocumented, relying on the reader's inference from the schema titles.

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?

Clearly states the verb (Set or patch) and resource (connection metadata), which distinguishes it from read-focused siblings like get_connection_context and tag-focused patch_connection_tags. No explicit sibling differentiation, but the intent is unambiguous.

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?

Provides a negative constraint ('Do not put credentials or required connection config here') which guides content selection, but offers no guidance on when to use this tool versus alternatives such as get_connection_context or patch_connection_tags. No explicit context or alternatives are mentioned.

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