xero_create_feed_connection

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

Annotations already declare this to be a non-read-only, idempotent, destructive operation, so the baseline burden is lower. The description adds some useful governance context: the call routes through a connector authority, the claimed effect is verified by Spring, and approval_ref is needed to resume a write. However, it does not describe the actual consequences of creating the feed connection or what destructive behavior the platform may perform.

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 argument list is compact and organized, but the first sentence repeats information already present in the tool name and namespace. The description could be shorter and clearer if that tautological opening were replaced with a real purpose statement.

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 mutating connector operation with seven parameters and no schema-level descriptions, key invocation details are missing: what a feed connection is, what belongs inside the arguments JSON, what effect values are valid, and when approval_ref is required. The presence of an output schema helps, but the input contract is still under-specified.

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 does provide one-line meanings for all seven parameters, including helpful notes like idempotency_key as a stable business-action identity and approval_ref as the approved platform task UUID when resuming a write. However, the most important parameter, arguments, is only described as a 'JSON string of arguments for the connector operation' with no indication of what that JSON should contain.

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 opens with 'Xero connector operation create_feed_connection', which essentially restates the tool name without explaining what a feed connection is or what creating one accomplishes. It does not distinguish this operation from the many other xero_create_* tools or from related xero_list_feed_connections / xero_delete_feed_connection siblings.

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?

No guidance is provided on when to use this tool versus alternatives. The only contextual statement is a routing constraint ('Routes only through the exact project/account governed connector authority'), which is an operational restriction rather than a usage criterion such as 'use this when you need to establish a new data feed connection'.

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