xero_list_currencies

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It fails to mention read-only nature, required permissions, side effects, or output characteristics. The description only covers technical routing.

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 (two sentences), but the first sentence is redundant (repeats name and platform tool). The routing information in the second sentence could be more concisely stated. It is adequately structured but not front-loaded with core purpose.

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?

Although an output schema exists (not shown), the description does not explain the expected input format (JSON arguments) or any requirements for the tool. For a list operation with a complex argument, the description is insufficient for an agent to 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?

The sole parameter 'arguments' is described generically as 'JSON string of arguments for the connector operation.' With 0% schema coverage, this adds minimal meaning beyond the schema and does not specify expected keys or structure for listing currencies.

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 does not explicitly state that the tool lists available currencies from Xero. It primarily repeats the tool name and describes routing details. The purpose is implied by the name but not reinforced in the description.

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 (e.g., other xero_list_* tools). There is no mention of prerequisites, context, or when it is appropriate to invoke this tool.

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