finance_xero_payroll_trueup

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

Annotations already indicate destructive/write behavior. The description adds that it routes through the domain-agent dispatcher under JWT, tenant, and company scope, giving additional context about execution environment and authorization scoping. No contradiction.

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 concise, including the action name, routing behavior, and parameter definitions in a compact format without extraneous content.

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 simple dispatch nature and presence of an output schema (not shown), the description is complete enough for an agent to invoke it. It provides routing, scoping, and parameter semantics.

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 schema provides only types and defaults with no descriptions, so the description's Args section adds meaning by defining 'message' as free-text objective and 'inputs' as optional JSON string. This compensates for the schema gap, though the explanations are somewhat generic.

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 specifies the verb 'Run' and the exact resource 'finance domain agent action xero_payroll_trueup', distinguishing it as an agent action versus direct Xero API tools among siblings. However, it does not explain what the trueup action does, so purpose is clear but not fully informative.

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 about when to use this tool versus alternative payroll or Xero tools. The description only states how to run it, not when. Thus no usage direction.

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