start_profiling

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

Describes rotation behavior and mutual exclusivity. With no annotations, it carries behavioral disclosure well but could mention side effects like overwriting old recordings more explicitly.

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?

Concise single paragraph packed with essential information. Every sentence adds value: core action, rotation, presets, customization, follow-up.

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?

Covers key aspects but lacks description of return value or output. For a complex tool with no output schema, describing the result (e.g., recording ID or success status) would improve completeness.

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?

Adds significant value beyond 100% schema coverage: default preset, mutual exclusivity, and event limitations of builtin presets. This helps agents choose between preset and settingsFile.

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?

Clearly states it starts JFR on a target PID and rotates recordings. Differentiates from sibling tools like list_java_processes, stop_profiling, and other profiling variants.

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?

Provides guidance on using preset vs settingsFile, their mutual exclusivity, and limitations of builtin presets. Suggests follow-up steps (list_jfr_recordings, stop_profiling). Lacks explicit when-not-to-use compared to sibling profiling tools.

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