JProfiler

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the tool initiates loading but doesn't complete it synchronously, requiring follow-up calls to 'check_status' and 'get_*' tools. However, it doesn't mention potential errors, timeouts, permissions needed for file access, or what happens if loading fails—important gaps for a tool with no annotation coverage.

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 highly concise and well-structured in two sentences. The first sentence states the purpose, and the second provides critical usage guidelines. Every word earns its place, with no redundancy or fluff, making it easy for an AI agent to parse quickly.

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?

Given the tool's complexity (asynchronous loading with dependencies) and lack of annotations/output schema, the description does a good job covering the essential workflow. It explains the purpose, required follow-up steps, and file types. However, it misses details like error handling or performance implications, leaving some gaps for a tool with no structured safety or output information.

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 the schema already documents both parameters ('filePath' and 'baselineFilePath') adequately. The description adds no additional parameter semantics beyond implying file types (.jps, .hprof, .jfr) and the analysis context. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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's purpose: 'Load an existing .jps, .hprof, or .jfr file for analysis.' It specifies the verb ('load'), resource (snapshot files with specific extensions), and high-level goal ('for analysis'). However, it doesn't explicitly differentiate from sibling tools like 'attach' or 'create_heap_dump' that might also involve snapshot handling.

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 provides explicit usage guidance: 'You must call check_status to check the loading progress and - after this returns 'data_ready' - retrieve data with the get_* tools.' This clearly states the required workflow and dependencies, including when to use this tool (initial loading) versus alternatives (status checking and data retrieval tools).

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