xero_create_feed_connection

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

No annotations provided. The description mentions routing through /api/tools/invoke and scope (JWT, tenant, company), but does not disclose side effects, idempotency, error scenarios, or what happens if the connection already exists.

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 short with two sentences and a parameter line. It is concise but uses jargon like 'connector operation' without explanation. The structure is acceptable but not enhanced.

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?

Despite having an output schema, the description lacks essential context: what exactly a feed connection is, what arguments are needed, and what side effects occur. It is insufficient for a user to confidently use the tool.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation', adding minimal meaning beyond the schema. It does not detail valid fields, formats, or examples, failing to compensate for 0% schema description coverage.

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 identifies the tool as a 'connector operation create_feed_connection', which implies creating a feed connection in Xero. However, it does not define what a feed connection is or distinguish it from siblings like list and delete. The purpose is only vaguely clear.

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 on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or compare with related operations like listing or deleting feed connections.

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