get_issue_with_stacktrace

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states what the tool returns, not error behavior, performance implications, response format, or any side effects. This leaves the agent with limited understanding of how the tool behaves in edge cases.

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?

The description is a single concise sentence that front-loads the verb and resource. It contains no filler or redundant information, earning a top score for structure.

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?

With no output schema and no annotations, the description fails to convey the full response structure beyond 'metadata' and 'stacktrace', and it omits error handling or when to use this tool vs alternatives. The tool's simplicity is not sufficiently documented, leaving important gaps.

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?

The schema fully describes the single parameter issue_id, including example format ('PAYOUT-A6Z'). Since schema coverage is 100%, the description adds no additional meaning beyond the schema, warranting the baseline score of 3.

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 verb 'Get' with specific resources 'issue metadata' and 'latest event stacktrace' makes the tool's purpose explicit. It clearly differentiates from siblings like get_issue (metadata only) and get_latest_event (event only) by emphasizing the combined single-call nature.

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?

The description implies usage when both metadata and stacktrace are needed in one call, but it never explicitly states when to prefer this over separate calls to get_issue and get_latest_event. No exclusions, prerequisites, or comparison with alternatives are provided.

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