Get bundle semantics

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

With no annotations, description carries behavior disclosure burden. It notes the block is 'when present' and lists returned fields, implying safe read operation. Lacks explicit statement of side effects, but read nature is clear.

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 with zero wasted words: first sentence lists content, second sentence provides usage alternatives. Front-loaded with key purpose.

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 tool with one optional parameter and no output schema, description fully covers what the tool returns (listing fields) and when to use it. 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?

Schema coverage is 100% for the single parameter, so baseline is 3. Description does not add parameter details beyond schema, which is acceptable as schema already explains bundleId's purpose and optionality.

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?

Clearly states it returns the bundle's pre-computed semantics block, listing specific fields (stateAtCapture, errorSummary, etc.). Distinguishes from siblings by advising to use find_errors/get_* for detailed drill-down.

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 recommends using this tool for UAT triage orientation and directs to alternative tools (find_errors, get_*) for per-event analysis, providing clear when-to-use and when-not-to-use guidance.

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