Get XRC owner summary

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

The description states it is 'read-only,' which implies non-destructive behavior, but with no annotations, it does not disclose any other behavioral traits like caching, latency, or rate limits.

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 a single, compact sentence that front-loads key information. Every word is functional, with no redundancy.

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 the lack of output schema and low parameter details, the description provides a minimal but adequate overview. It could be improved by specifying what the summary includes (e.g., balances, counts).

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 'owner' has no schema description, and the tool description merely restates 'for an owner' without adding format or usage details beyond the regex pattern.

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 clearly specifies the action (get compact summary), resource (XRC-137/XRC-729 assets and recent XRC events), and scope (for an owner). It effectively distinguishes from sibling tools like get_xrc_contract_events or get_xrc_usage.

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 alternatives, such as when an owner needs a high-level overview versus detailed event logs or statistics.

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