browser_perf_stop_profile

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states it stops profiling and gets data, but does not explain side effects (e.g., whether data is returned in the response, if profiling state is reset, or if calling without a prior start causes an error). The reference to 'browser_docs' partially substitutes, but the description itself is insufficient. Score 2.

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 extremely concise at one sentence with a link to docs. It is front-loaded with the action. However, it could be slightly more informative without losing conciseness. Score 4 for appropriate brevity.

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 simplicity (no parameters, no output schema), the description provides the essential action but lacks context about pairing with browser_perf_start_profile and the nature of the returned profile data. It is minimally adequate but leaves gaps. Score 3.

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 tool has zero parameters, and the schema coverage is 100% (empty schema). The description adds no parameter information because none is needed. Baseline for 0 parameters is 4, and the description meets that standard.

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 CPU profiling and get profile data. It references 'browser_docs' for details, which helps. However, it doesn't explicitly distinguish from sibling tools like browser_perf_stop_coverage, though the resource 'CPU profile' is unique. Score 4 because it's clear but not fully specific about what 'profile data' entails.

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 this tool is used after starting a CPU profile, but it does not explicitly state that a profile must have been started first, nor does it mention when not to use it. No alternatives are discussed. Score 3 for implicit usage but lack of explicit guidance.

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