xero_agent_snapshot

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

No annotations provided, so the description must fully disclose behavioral traits. It only implies reading ('snapshot') but does not explicitly state it is read-only, mention authentication needs, data freshness, scope limitations, or any side effects. The description fails to add value beyond the basic purpose.

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?

Two sentences with no wasted words. The first sentence captures the tool's purpose and scope, the second explains the optional parameter. Efficient and well-structured.

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 tool's complexity (multi-org snapshot with multiple financial components), the description is adequate. It lists the components covered and the filtering option. The output schema exists, so the return format does not need to be described. Slight omission: no mention of whether the snapshot is real-time or cached.

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 input schema has one parameter 'body' typed as string with no description. The description adds full semantics by explaining it expects a JSON object of filters, providing an example with 'xero_tenant_ids'. This completely compensates for the 0% schema coverage.

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?

Description clearly states the tool retrieves a multi-org Xero financial snapshot covering cash, AR, AP, payroll, and taxes. It uses a specific verb-resource combination ('snapshot') and distinguishes itself from sibling Xero tools by mentioning 'Multi-org' and the comprehensive scope.

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 alternatives like xero_balance_sheet_report or xero_cash_flow_report. There is no mention of prerequisites, when not to use, or which other tools might be better suited for specific financial details.

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