xero_gst_report

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

No annotations are present, yet the description does not disclose behavioral traits like idempotency, rate limits, authentication requirements beyond routing detail, or what the report returns. The description fails to shoulder the burden left by missing annotations.

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 inefficient: the first sentence is a tautology, and routing details about JWT and scopes are not agent-relevant. Every sentence does not earn its place.

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, the description does not describe the report's content or purpose. Given the abundance of sibling report tools, this description leaves the agent without enough context to discriminate or use correctly.

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?

With 0% schema description coverage, the description only states that the argument is a JSON string, without explaining expected keys or structure. This adds minimal value over the schema's type definition.

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 restates the tool name as 'Xero connector operation gst_report' without specifying what the GST report does. It lacks a verb-resource combination and fails to distinguish from sibling report tools like xero_bas_report or xero_balance_sheet_report.

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 other Xero reporting tools. There is no mention of prerequisite conditions, exclusions, or comparative scenarios.

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