update_surface_connection

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

Comprehensively discloses behavior: no id, index-based selection, only provided parameters change (others unchanged), and return value description. No annotations provided, so description carries full burden and does so effectively.

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?

Well-structured with introductory paragraph and clear parameter list. Slightly verbose with None repetition, but overall efficient and front-loaded with key info.

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?

Fully explains all parameters, selection mechanism, and return value. Given no output schema (but annotation says it exists), the description covers what the agent needs to use the tool correctly.

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?

Despite 0% schema description coverage, the description includes a full parameter list with explanations for each, adding significant meaning beyond the bare schema definitions.

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 'Update an existing surface connection' and explains the index-based selection due to lack of id, distinguishing it from sibling update tools that use ids.

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 clear context on how surface connections are selected by index and which parameters change. Could be improved by explicitly stating when not to use (e.g., if id available), but the use case is straightforward.

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