xero_update_contact

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

No annotations are provided, so the description carries full burden for behavioral traits. It fails to disclose any side effects, idempotency, required permissions, or what happens when a contact is updated. The routing detail is not behavioral insight.

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 consists of three short sentences, but the first is tautological (restates name), the second provides routing info that may not help an agent decide, and the third minimally describes the parameter. It is concise but lacks substantive 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 that the tool updates a Xero contact (potentially many fields) and has an output schema, the description is insufficient. It does not explain what the tool returns or any important context like required contact ID. The minimal text leaves significant gaps for an AI agent.

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 is 'arguments' (a JSON string). The description says 'JSON string of arguments for the connector operation' but does not specify the expected structure or fields. With 0% schema description coverage, the description fails to add meaningful guidance beyond the schema's 'Arguments' title.

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 'update_contact' which implies updating a contact in Xero, but it doesn't specify what fields can be updated or how it differs from related tools like xero_create_contact. The name itself provides moderate clarity, but the description adds no additional differentiation.

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 only mentions routing details ('Routes through /api/tools/invoke under your JWT, tenant, and company scope') and does not provide any guidance on when to use this tool versus alternatives like xero_create_contact or xero_list_contacts. No 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.