xero_create_manual_journal

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

With no annotations, the description carries full burden but fails to disclose behavioral traits. It mentions routing details (JWT, tenant, company scope) but does not describe that the tool performs a mutation (creating a journal), required permissions, side effects, or error states.

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 relatively short but includes unnecessary routing details that do not help the agent understand the tool's purpose. It is not well-structured for quick comprehension; the most relevant information (that it creates a manual journal) is not front-loaded.

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 (unseen), the description lacks completeness. It does not explain what the tool returns, what data is required in the arguments JSON, or any expected behavior. For a creation tool with one opaque parameter, this is severely 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 input schema has 0% description coverage, and the description only restates that the 'arguments' parameter is a JSON string for the connector operation. It provides no information about the expected keys, structure, or content of the JSON, leaving the agent without meaningful guidance.

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 merely states 'Xero connector operation create_manual_journal' which is a tautology of the tool name. It does not explicitly state that the tool creates a manual journal entry, nor does it describe what a manual journal is or what the tool accomplishes.

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 such as xero_list_manual_journals or xero_update_manual_journal. There is no mention of prerequisites, context, or exclusions.

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