modify_connection_state

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

Flags as write operation with warning. Describes required pre-condition (pause connection). Specifies supported connector types. No annotations provided, so description carries full burden; it adequately discloses behavioral constraints.

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?

Description is somewhat verbose, repeating phrases like 'To update the connection state.' Includes inline links and steps that could be streamlined. Front-loaded with warning, but overall could be more concise.

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?

Covers process steps and connector limitations. Lacks information about return values or error responses since no output schema. Given complexity and sibling tools, description is adequate but not fully complete.

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 coverage is 100%, baseline 3. Description adds value by instructing to read schema file for 'schema_file' parameter and explaining 'request_body' references schema. This goes beyond repeat of schema fields.

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 'Updates the connection state.' It distinguishes from sibling tools like 'connection_state' (likely a getter) and 'modify_connection' (different operation). Also specifies it's only for Function and Connection SDK connectors, adding 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?

Provides explicit steps: pause connection, update state, unpause. Includes a warning to confirm with user before calling. Does not explicitly exclude scenarios or offer alternatives, but gives clear context for typical usage.

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