JProfiler

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the multi-step workflow (dump → check_status → get_heap_data), the requirement to monitor progress, and the dependency on other tools. However, it doesn't mention potential side effects (e.g., performance impact on JVM during dump) or error conditions.

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 appropriately sized and front-loaded, starting with the core action and immediately following with essential workflow instructions. Every sentence provides necessary information about the tool's operation and dependencies, though it could be slightly more streamlined by combining some workflow details.

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 (multi-step workflow with dependencies) and no annotations or output schema, the description does well by explaining the process flow and required follow-up actions. However, it could benefit from mentioning what happens after loading (e.g., analysis capabilities) or typical use cases to provide more complete context.

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 fully documents both parameters (pid and containerNameOrId). The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

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 with specific verbs ('dump', 'load') and resources ('heap of a locally running JVM or of a JVM inside a Docker container', 'HPROF file'). It distinguishes from siblings by specifying this is for heap dumping and analysis, unlike list_jvms (discovery) or get_heap_data (retrieval).

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 guidance on when to use this tool: for dumping and loading heap data from JVMs, with prerequisites (call check_status for progress, use get_heap_data after data_ready, use list_jvms for discovery). It clearly distinguishes from alternatives by naming specific sibling tools for different steps in the workflow.

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