get_latest_event_stacktrace

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

Annotations already mark the tool read-only, idempotent, and non-destructive, and the description adds useful behavioral detail: the result includes source and locals, and continuation cursors stay pinned to the event. It does not mention failure modes or side effects, but the safety profile is already covered by 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 concise sentences with the primary action front-loaded. Every sentence adds meaningful detail, with no redundancy or extraneous content.

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?

Adequate for the main purpose, but incomplete for a tool with three parameters and no output schema. max_chars is never mentioned, cursor mechanics are only implied, and the relationship to the sibling get_event_stacktrace tool is not addressed.

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 only 33%, with only issue_id described. The description mentions continuation cursors generally but never explicitly explains the cursor parameter or the max_chars parameter, leaving important parameter semantics under-specified.

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 identifies a specific read operation: fetching the newest stored event’s stacktrace as rendered text with source and locals. The phrase 'newest stored occurrence' distinguishes it from generic event or stacktrace retrieval siblings.

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?

Conveys when to use it—when the newest stored occurrence is needed with rendered text, source, and locals—and adds useful context about pinned cursors. It does not explicitly contrast with get_event_stacktrace or list_events, but the 'newest' scope provides clear situational guidance.

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