analyze_thread_dump

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

With no annotations, the description carries full burden. It discloses a significant limitation: deadlock detection only covers synchronized monitor locks, not j.u.c locks. This transparency about behavioral constraints is valuable.

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, each earning its place: first sentence states purpose, second mentions virtual thread support, third discloses limitation. No unnecessary words, well-structured.

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?

The description lacks information about the output format or what the tool returns. Without an output schema, an AI agent would not know what to expect. The description covers input well but omits output details.

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 single parameter 'thread_dump' has 100% schema coverage. The description adds context by naming common sources (jstack, kill -3, VisualVM) and specifying the accepted format, going beyond the schema's generic description.

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 specific verbs 'Parse... and analyze' and clearly identifies the resource as a 'JVM thread dump (jstack output)'. It lists specific analysis goals (deadlocks, lock contention, thread starvation) which distinguishes it from sibling tools like analyze_jfr or analyze_gc_log.

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 for thread dump analysis scenarios but does not explicitly state when to use this tool over alternatives. However, the clear purpose differentiates it from siblings, providing implicit guidance.

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