analyze_xero_journal_anomalies

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

Discloses input limits (max 5,000 rows, 5 MB), output structure (flagged lines with severity and URL), and that it is not history-aware (advanced checks in paid product). With no annotations, description fully shoulders transparency burden.

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?

Packed with essential information in a structured flow: purpose, input, constraints, output, usage scenarios, and differentiation. No wasted sentences.

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?

Comprehensive coverage given no output schema or annotations: explains input format, output details, constraints, usage context, and limitations (only round numbers, not history-aware). Completeness is high.

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 provides full descriptions for both parameters (100% coverage). Description adds constraints (max rows/size) not in schema, but no other substantive new meaning beyond schema.

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?

Clearly states it scans Xero Manual Journals CSV for round-number anomalies, specifying input source, what anomalies it finds, and output (flagged lines with severity and shareable URL). Distinguishes from sibling tools by mentioning QBO variant and paid product for advanced checks.

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?

Explicitly says 'Use this when a user pastes Xero data and asks any anomalies?, look for round numbers, or anything suspicious.' Contrasts with paid product for deep analysis, providing clear when-to-use and when-not-to-use guidance.

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