xero_create_asset

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

With no annotations, the description carries the burden. It mentions routing but not behavioral traits like idempotency, side effects, required permissions, or what happens on duplicate. Does not disclose that the arguments must match Xero's create asset API structure.

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 short but includes routing details that may be extraneous for an agent. No wasted words overall, but could be more focused on core behavior. Structure is a single paragraph, which is acceptable.

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 reference it or explain return values. For a create tool, it lacks context on how to construct the arguments, what the expected outcome is, and operational details. Incomplete for an agent to use effectively.

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% (no parameter descriptions). The description says 'JSON string of arguments for the connector operation,' which adds minimal value by indicating type but not the expected structure or required fields. Fails to compensate for the schema gap.

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 is a 'create_asset' operation for Xero, implying creation of an asset. However, it doesn't explicitly state 'Creates an asset in Xero' or describe what an asset is in this context. It distinguishes from siblings like xero_get_asset (retrieve) but lacks specificity, making it adequate but not excellent.

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 alternatives (e.g., xero_create_bill, xero_create_invoice). No prerequisites or context provided. The description only mentions routing details, not usage scenarios.

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