profiler_stop

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

With no annotations, the description conveys the full behavioral intent: stopping, saving to a file, returning path or null. It adds context about the download directory and return value beyond the schema. However, it could mention error handling if no profiler is running.

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?

Two sentences, no fluff. Front-loaded with action and outcome, then return value. Every sentence earns its place.

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?

For a simple tool with one optional parameter and no output schema, the description covers the main behavior and return. Could mention prerequisites (profiler must be running) or file naming, but overall adequate.

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 coverage is 100% (single parameter 'discard' described). The description does not add extra meaning beyond what the schema provides. Baseline 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 action 'Stop' and the resource 'Firefox profiler', and specifies what happens: save to file, return path. This distinguishes it from siblings like profiler_start and profiler_is_active, which start or check status.

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 usage is implied as complementary to profiler_start, but the description does not explicitly state when to use this tool versus alternatives (e.g., profiler_is_active) or mention prerequisites like needing an active profile. No guidance on exclusions.

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