xero_create_contact

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

The description mentions routing through /api/tools/invoke under JWT/tenant/company scope, which gives some authentication context. However, it does not disclose side effects, required permissions, rate limits, or what happens during creation (e.g., duplicates, validation). With no annotations, the description carries the full burden but fails to provide sufficient behavioral detail.

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 very short and front-loaded, but it lacks necessary detail. Conciseness is not sacrificed for completeness, but here it is too terse. It could be more informative while remaining concise.

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 that this is a create operation with a complex underlying API (Xero contacts), the description is woefully incomplete. It omits information about required fields, argument structure, return values, error handling, and typical usage context. The output schema exists but is not explained.

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 only parameter 'arguments' is a JSON string with no schema description coverage (0%). The description merely says 'JSON string of arguments for the connector operation'—this adds negligible meaning. The agent cannot infer what keys or structure the JSON should contain.

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 it creates a contact in Xero, but gives no specifics about what a Xero contact represents (e.g., customer, supplier). It is a verb+resource but lacks depth and does not distinguish from sibling tools like xero_create_invoice or xero_create_bill.

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 other Xero create operations. No prerequisites, exclusions, or alternatives mentioned. The description provides no contextual help for selecting the right tool.

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