frida_stalker_add_call_probe

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

The description states it adds and removes a probe, but does not disclose side effects (e.g., whether it logs calls, impacts performance, or requires specific permissions). Without annotations, this is insufficient.

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 a single short sentence, but it is under-specified rather than concise. It omits critical details and does not earn its place by providing 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 tool with 3 parameters and no output schema, the description should explain what the probe does, how duration_seconds affects behavior, and what the return value is. It fails to do so.

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 0% and the description does not explain any of the three parameters (target, address, duration_seconds). The agent cannot infer what each parameter represents.

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 mentions calling Stalker.addCallProbe() and removing it, which indicates the basic action but does not clarify the purpose of the probe (e.g., monitoring function calls). It is slightly above tautology but lacks functional explanation.

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 versus alternatives like frida_stalker_configure, frida_stalker_coverage, or other hooking tools. The description provides no context for selection.

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