set_connection_metadata

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

No annotations are present, so the description must fully disclose behavior. It only states the basic operation (set/patch) and warns about credentials, but fails to mention side effects (e.g., whether existing metadata is overwritten or merged), permissions required, idempotency, or triggered events.

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 very short (two sentences) and front-loads the purpose. However, it is overly terse: it could include brief parameter guidance or usage context without becoming verbose. It is concise but at the expense of completeness.

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 6 parameters (4 required), no output schema, and no annotations, the description is inadequate. It fails to explain the role of 'patch', 'confirmation', or the structure of 'metadata'. The tool appears complex (nested objects) yet the description provides minimal context.

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 description adds no parameter-level meaning. With 0% schema description coverage, the schema only lists names and types. Parameters like 'patch', 'confirmation', and 'metadata' (a complex nested object) are entirely undocumented. The high-level warning does not clarify individual 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 clearly states the verb ('Set or patch') and the resource ('connection metadata'), distinguishing it from sibling tools that modify other aspects of connections (e.g., patch_connection_tags, delete_connection). The warning about credentials adds specificity.

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 provides a single prohibition (don't put credentials/config) but offers no guidance on when to use this tool versus alternatives like patch_connection_tags or update_integration. No explicit context or exclusion criteria are given.

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