xero_list_linked_transactions

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

The description briefly mentions routing through the API under JWT, tenant, and company scope, which offers some authorization context. However, it does not disclose whether the tool is read-only, whether it has side effects, or any pagination/limitation behavior.

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 very short (three sentences), which is concise, but it sacrifices necessary detail. The front-loading is minimal, with the first line being a tautological restatement of the name.

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 simplicity of the tool (one parameter, no annotations), the description still fails to provide enough context for an agent to use it effectively. The presence of an output schema is not leveraged in the description, and the lack of any behavioral or parameter detail makes it incomplete.

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 is a generic 'arguments' JSON string with a default '{}'. The description merely repeats that it is a JSON string of arguments for the connector operation, providing no details on the expected structure or fields. With 0% schema coverage and no additional explanation, this is extremely unhelpful.

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 restates the tool name and mentions it's a Xero connector operation, but does not define what 'linked transactions' are in Xero. It fails to differentiate itself from other Xero list tools, though the name provides some inherent meaning.

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, nor are there any prerequisites or usage context mentioned. The agent is left guessing when to invoke it.

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