JProfiler

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

With no annotations provided, the description carries the full burden. It discloses that the tool can stop recordings and provides subsystem information when data is ready, which are useful behavioral traits. However, it lacks details on permissions needed, rate limits, error conditions, or what happens if no session exists, leaving gaps for a mutation-capable tool.

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 with three sentences that each add value: stating the primary purpose, mentioning the stop functionality, and detailing the output when data is ready. It's front-loaded with the core function, though it could be slightly more structured by separating usage scenarios.

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 moderate complexity (one optional parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the main actions and output examples, but doesn't explain return values fully (e.g., format, error responses) or address all behavioral aspects like side effects, making it adequate but not comprehensive.

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 input schema has 100% description coverage, with one parameter ('stopRecording') fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as examples or edge cases. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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: checking the status of a profiling session and discovering recorded subsystems. It specifies the resource (profiling session) and the action (check status, discover subsystems). However, it doesn't explicitly differentiate this tool from its siblings like 'list_jvms' or 'get_performance_hotspots', which prevents a perfect score.

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 context by mentioning 'Can be used to stop recording' and 'When the data is ready...', suggesting it's for monitoring ongoing profiling sessions. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_performance_hotspots' or 'load_snapshot', nor does it specify prerequisites or exclusions.

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