xero_list_assets

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

The description discloses that the tool routes through /api/tools/invoke under JWT, tenant, and company scope, providing authentication context. However, it does not mention any side effects or confirm it is a read-only operation, and no annotations are present to supplement.

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 (two sentences plus args line), which is concise, but it lacks substantive content about the tool's purpose and behavior. It is not well-structured to be informative.

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 only one parameter and no output schema, the description omits critical details such as what the tool returns (list of assets) and any constraints. It is incomplete for effective use.

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 description restates the schema's single parameter as 'JSON string of arguments' without adding any detail about expected keys or content. With 0% schema description coverage, this adds minimal value beyond the schema itself.

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 Xero connector operation 'list_assets' but provides no business-level explanation of what listing assets entails. It only gives technical routing details, leaving the purpose vague for an AI agent.

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 is provided on when to use this tool versus siblings like xero_list_asset_types or other list tools. There is no mention of context, filtering, or alternatives.

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