sui_get_object

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

With no annotations, the description carries full burden. It discloses the 'auto' routing's fallback behavior to Archival Service for expired versions and mentions the trace recording. It is transparent about a non-obvious behavior (version non-monotonicity caveat).

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?

Three sentences with zero waste. The first sentence gives core purpose, the second lists returned fields and use case, the third explains routing and trace. Every sentence earns its place.

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 no output schema, the description thoroughly covers what is returned. Combined with excellent parameter documentation, it provides complete context for a single-object fetch tool. No gaps remain.

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?

All 4 parameters are fully described in the schema (100% coverage). The description adds significant value beyond the schema by explaining the version parameter's non-monotonic nature with a detailed example, and the source parameter's practical routing intent. This aids correct invocation.

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 begins with a clear action verb 'Fetch' and specifies the resource 'Sui object's current state by object id'. It lists the returned fields (owner, type, version, etc.), distinguishing it from sibling tools like sui_batch_get_objects or sui_get_transaction.

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?

It explicitly states 'Use for any "what is object 0x..." question — bypass GraphQL for single-object reads', giving clear when-to-use guidance. It also explains routing policies and when to force specific sources. It lacks explicit when-not-to-use, but the sibling list implies batch for multiple objects.

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