xero_profit_loss_report

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

No annotations provided. The description does not disclose whether the tool is read-only, idempotent, or any behavioral traits such as required permissions or side effects. It only mentions routing details.

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 but includes repetitive information (e.g., full tool name mentioned twice). It could be more concise by removing redundant boilerplate while maintaining clarity.

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 lack of parameter documentation and behavioral details, the description is incomplete for a report tool. Although an output schema exists, the description does not hint at what the report contains, leaving the agent with insufficient context.

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 merely as 'JSON string of arguments for the connector operation.' With 0% schema description coverage, no additional meaning is added. The description fails to specify required keys or structure for the arguments JSON.

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 'profit_loss_report' but does not explicitly define what a profit and loss report is or use a clear verb like 'retrieve' or 'get'. The purpose is somewhat clear from the name but the description lacks explicit specification.

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 other Xero report tools (e.g., balance sheet, cash flow). The description does not differentiate the use case or provide context for selection among sibling tools.

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