performance_trace_stop

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

The description explains the output format and save location. It implies a non-destructive stop. No annotations provided, but the description itself is fairly clear about what happens.

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 concise sentences, front-loaded with the core action. No unnecessary words.

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 stop action with one optional parameter and an output schema, the description covers the main behavior. However, it does not explain the filename parameter or potential errors.

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 single optional parameter 'filename' is not explained at all in the description. Schema coverage is 0%, and the description adds no meaning beyond 'filename'.

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 active performance trace' and specifies the destination 'save to ~/.mcp-stealth/exports/', which distinguishes it from sibling tool performance_trace_start.

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?

No guidance on when to use this tool or prerequisites (e.g., a trace must be started first). No mention of alternatives or when not to use it.

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