Get Raw XLog

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is known. The description adds behavioral context by noting the output is 'raw' with 'hash IDs' and that one mode is 'real-time streaming', giving useful expectation beyond annotations. The bar is lower due to annotations, and this description adds meaningful detail without contradiction.

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, front-loaded with the core action, and no filler. Each sentence earns its place: what it does, how it differs, and a useful pointer to a sibling tool.

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 complexity (18 params, 5 modes) and lack of output schema, the description provides a solid high-level overview, including return type hint ('raw XLog objects with hash IDs') and mode categories. It doesn't dive into streaming/pagination details, but the schema descriptions cover those, making it adequate.

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 100% (18 params fully described), so baseline is 3. The description enhances parameter understanding by grouping modes and explicitly linking hash ID parameters to lookup_text ('Use lookup_text to resolve hash IDs'), which goes beyond the schema's per-field descriptions.

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 uses a specific verb ('Get') and resource ('raw (non-decoded) XLog transaction data'), clearly differentiating from search_transactions. It also lists the five distinct modes, making the scope unmistakable and distinguishing it from sibling tools.

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?

Explicitly states 'Unlike search_transactions which returns decoded data' as a direct when-not/alternative. Also directs users to lookup_text for resolving hash IDs, providing a concrete next-step. This meets the explicit when/when-not/alternatives criterion.

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