finance_xero_org_overview

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

With no annotations, the description must disclose behavioral traits. It mentions routing through a domain-agent dispatcher and authentication scope, but does not state whether the tool is read-only, has side effects, or what permissions are needed. The agent gets little insight into the tool's behavior.

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 and uses a clear argument list. However, the first sentence is redundant with the tool name. Overall, it is acceptably concise.

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 mention what the tool returns. For a tool that likely retrieves organizational data, the description omits any indication of the output structure or typical use cases, leaving gaps in the agent's understanding.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'message' as 'Free-text objective' and 'inputs' as 'Optional JSON string of structured inputs'. This provides some meaning, but lacks details on how to properly use these parameters or what values are expected.

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 'Run the finance domain agent action xero_org_overview' and does not explain what the action does. It fails to specify that it retrieves an overview of a Xero organization, leaving the agent to infer purpose from the tool name alone. This is nearly a tautology.

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 the many other Xero tools (e.g., xero_get_organisation, xero_executive_summary_report). The description lacks context for selecting this tool over alternatives.

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