native-profiler-stop

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

With no annotations provided, the description fully discloses behaviors: platform-specific signals (SIGINT for iOS, SIGTERM for Android), polling, file export, return format, and failure condition. This provides comprehensive 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, well-structured, and front-loaded with the main action. Each sentence provides essential information without redundancy, effectively using bullet-like formatting for platform details.

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 complexity (platform-specific behavior, prerequisites, return type), the description is complete. It covers return shape, failure conditions, and usage context, despite lacking an output schema.

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% and the schema already describes device_id. The description adds value by tying device_id to the failure condition ('Fails if no active native-profiler-start session exists for the given device_id'), reinforcing its role beyond the schema.

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 'Stop native profiling and export trace data', specifying the action and resource. It distinguishes from siblings like native-profiler-start and native-profiler-analyze by detailing the stop and export process.

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?

Explicitly instructs to 'Call native-profiler-start first' and provides context for use: 'Use when the user has finished the interaction to profile'. It also notes failure if no active session, guiding correct invocation.

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