xero_trial_balance_report

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 does not disclose behavioral traits such as whether the tool is read-only, its impact, rate limits, or required permissions. The routing details are not behavioral traits.

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 (three sentences) and front-loaded with the tool name. However, it includes verbose routing details ('Routes through...') that are likely redundant for an agent with context, making it slightly less efficient than ideal.

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 complexity of a trial balance report tool and the presence of an output schema, the description fails to guide the agent on how to use the input parameter or what to expect at a high level. The lack of parameter guidance and behavioral info makes it incomplete for effective selection and 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 only parameter, 'arguments', is a JSON string with no schema descriptions (0% coverage). The description repeats 'JSON string of arguments for the connector operation' without explaining the required structure, keys, or examples. This provides no additional meaning over the schema itself.

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 states it is a 'Xero connector operation trial_balance_report', which combined with the tool name suggests it retrieves a trial balance report. However, it does not explicitly state the action (e.g., 'retrieve', 'generate') and lacks detail on what the tool returns. Among sibling tools like xero_balance_sheet_report and xero_profit_loss_report, the name differentiates, but the description offers no clarification.

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 when-to-use or when-not-to-use guidance is provided. The description only gives routing information (JWT, tenant, company scope) and does not differentiate this tool from other Xero report tools or state prerequisites.

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