Get Distributed Trace

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

Annotations already provide readOnlyHint/idempotentHint/destructiveHint, so the bar is lower. The description adds the scope (across services, multiple via txids) but no additional behavioral details like rate limits or response shape. Consistent with annotations.

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?

Two sentences, front-loaded with the core purpose, and every word is informative. No filler.

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?

For a read-only, well-annotated tool with full schema coverage, the description covers the core use cases and prerequisite flow. It doesn't explain return format, but given annotations and schema richness, it's sufficiently complete. Slightly less comprehensive than the TDQS 4.3 example.

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 description coverage is 100%, so baseline is 3. The description does not add parameter-level details beyond the schema; it merely mentions GXID and txid list, which are already documented. No additional semantic value.

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 states the tool traces distributed transactions across services via GXID or fetches multiple by txid list. It uses an active verb and specifies the resource (distributed trace), distinguishing it from sibling tools like get_transaction_detail.

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?

Explicit context is given: 'Essential for MSA environments' and 'Use after finding a GXID in get_transaction_detail' provides a clear when-to-use and a related tool. It lacks explicit exclusions or when-not-to-use, so it falls short of a 5.

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