profiler_start

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

The description discloses the constraint that preset and explicit options cannot be combined, and notes that the activeContext parameter does not restrict profiling to that tab. No annotations were provided, so the description carries full responsibility for behavioral transparency.

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 concise with three sentences, starting with the main action. It uses clear language with no redundant phrases.

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 6 parameters and no output schema, the description covers the essential behaviors and constraints. It could mention what happens after starting (e.g., returns a profile ID), but overall it is sufficient for calling the tool.

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 for all parameters. The description adds value by explaining the two usage modes and the constraint, supplementing the schema declarations.

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: 'Start the Firefox profiler.' It specifies two modes (preset or explicit options) and lists valid presets. This distinguishes it from sibling tools like profiler_is_active and profiler_stop.

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 explains when to use a preset versus explicit recording options and notes they cannot be combined. It lists valid presets. However, it does not provide explicit when-not-to-use scenarios or compare directly with alternatives.

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