xero_list_feed_connections

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

No annotations are provided, so the description carries the full burden. It mentions routing under JWT/tenant/company scope, which is somewhat behavioral, but fails to state that the operation is read-only, what side effects exist (likely none), or any rate limits. For a list tool, these omissions are notable.

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 (two sentences + one line) and front-loads the tool name. However, it includes unnecessary routing details (e.g., 'Routes through /api/tools/invoke') that an agent likely does not need. This detracts from conciseness and focus.

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 the tool's low complexity, zero schema coverage, and absence of annotations, the description is incomplete. It does not mention the output (though an output schema exists), pagination, or any special behavior. The agent lacks sufficient context for correct invocation.

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 schema has 0% description coverage for the single parameter 'arguments'. The description says 'JSON string of arguments for the connector operation,' which adds minimal meaning. It does not explain valid keys, formats, or provide examples, leaving the agent without guidance for constructing the parameter.

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 identifies the tool as a list operation for feed connections ('Xero connector operation list_feed_connections'). The verb 'list' and resource 'feed connections' are explicit, and the tool is distinct from siblings like xero_create_feed_connection and xero_delete_feed_connection. However, it does not explain what a feed connection is or what the output contains, slightly reducing clarity.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions. With many Xero list tools available, the lack of usage direction hinders correct selection.

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