xero_get_asset

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

The description mentions routing through JWT, tenant, and company scope, which is a minor behavioral detail. However, it discloses nothing about the operation being read-only, required permissions, or potential side effects. With no annotations, this is insufficient.

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 contains redundant routing information that likely applies to all Xero tools. It wastes space without adding tool-specific value. A more focused description would state what the tool gets.

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 the simplicity of a get operation, the description is completely inadequate. It does not specify the return value, required arguments, or how it differs from related tools. An agent cannot use this tool correctly based on this description.

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 single parameter 'arguments' is described only as 'JSON string of arguments for the connector operation.' With 0% schema coverage, the description must provide detail on expected keys (e.g., asset ID), but it does not, making the parameter effectively opaque.

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 `get_asset`' without explaining what an asset is in Xero context or what the tool does. It fails to specify that it retrieves a specific fixed asset, which is a critical omission.

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 its siblings, such as `xero_list_assets` for listing assets. The description does not mention prerequisites, context, or exclusions.

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