finance_stripe_xero_writeback_fanout

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

No annotations are provided, so the description bears full responsibility. It does not disclose side effects (likely writing to Stripe/Xero), destructive potential, auth requirements beyond generic scoping, or rate limits. The behavioral impact is completely opaque.

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 with three short paragraphs and a clear 'Args' section. Information is front-loaded. No unnecessary words, but the Args section could be more informative without adding length.

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 and two optional parameters, the description lacks essential context about the tool's purpose, effects, and usage scenarios. The name suggests a coordination between Stripe and Xero, but the description does not elaborate, leaving the agent with insufficient information to decide when to invoke it.

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?

With 0% schema description coverage, the description must compensate. It defines 'message' as free-text objective and 'inputs' as optional JSON string, adding minimal meaning beyond the schema defaults. No constraints or formatting hints are provided, leaving the agent under-informed.

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 states 'Run the finance domain agent action stripe_xero_writeback_fanout', clearly identifying the verb and resource. However, it does not explain what the action actually does operationally (e.g., writeback from Stripe to Xero), and fails to differentiate from numerous sibling tools with similar names.

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?

The description mentions routing through a domain-agent dispatcher under JWT/tenant/company scope, but provides no guidance on when to use this tool versus alternatives (e.g., direct Stripe or Xero tools). No explicit when-to-use or when-not-to-use information is given.

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