xero_update_item

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

No annotations provided; the description only states it updates an item and mentions authentication routing, but does not disclose side effects, required permissions, error conditions, or whether it's destructive. Without annotations, the description fails to compensate.

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 (three sentences) and front-loaded with the name and routing, but it sacrifices informative value for brevity. Appropriate length given the low information density.

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, the description does not hint at return values or expected behavior. For an update operation, crucial details like whether the item must exist, what fields are updatable, and confirmation of success are missing.

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%; the description adds that `arguments` is a 'JSON string of arguments for the connector operation' but does not specify which fields are expected or their formats. This provides minimal additional meaning beyond the raw schema.

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 merely restates the tool name as 'Xero connector operation `update_item`' without explaining what an 'item' represents in Xero or distinguishing it from `xero_create_item`. No verb-resource clarity beyond the name itself.

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 vs alternatives like `xero_create_item` or `xero_list_items`. No mention of prerequisites, required item existence, or common use cases.

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