xero_intake_payroll_trueup

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

The description discloses that the tool is HITL-gated, but lacks details on side effects, idempotency, or what happens after proposing (e.g., creation of a pending action). With no annotations, the description should provide more behavioral context.

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 at one sentence, front-loading purpose and gating. However, it lacks any additional structure or detail that would improve usability without being overly verbose.

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 complexity of a payroll true-up tool with a JSON body input and an output schema, the description is severely incomplete. It does not explain what the output represents, expected JSON keys, or how the proposal is processed, leaving the agent with insufficient information.

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 coverage is 0%, so the description must compensate. It states 'Body is JSON', which adds that the string parameter should be JSON, but does not specify the expected structure, required fields, or provide examples. This is insufficient for correct invocation.

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 clearly states the tool proposes a payroll true-up into Xero, using a specific verb and indicating HITL gating. However, it does not distinguish from similar siblings like finance_xero_payroll_trueup or other intake tools, and 'payroll true-up' may not be universally understood without context.

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, such as xero_intake_bill or finance_xero_payroll_trueup. There is no mention of prerequisites, exclusions, or context for appropriate use.

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