profiler_stop

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

With no annotations, the description must fully disclose behavior. It reveals the save-to-file action, the directory, and the return value. However, it does not cover edge cases like what happens if no profile is active, file naming conflicts, or whether the action is synchronous. The description is adequate but not thorough.

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 two sentences long, no unnecessary words, and front-loads the primary action. Every sentence adds value.

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 parameter and no output schema, the description covers the essential behavior and return value. It lacks some context (e.g., prerequisites, error handling) but is complete enough for an agent to understand the main functionality.

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%, so the parameter description is already in the schema. The tool description does not add any additional semantics beyond the schema's own description of the 'discard' parameter. It is a baseline score as the description adds no extra value.

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 the Gecko profiler'), the result ('save the recorded profile to a file in the downloads directory'), and the return value ('path to the saved file, or null'). It distinctly separates from sibling tools like profiler_start and profiler_is_active by using the verb 'stop' and specifying saving.

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 does not state when to use this tool, such as requiring the profiler to be running first, or when not to use it (e.g., if already stopped). The optional 'discard' parameter is mentioned but not contrasted with normal save behavior. No alternatives or exclusions are provided.

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