frida_stalker_invalidate

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

No annotations provided, and the description does not disclose behavioral traits such as side effects, permissions needed, or what state is modified. For a tool that likely invalidates some stalker state, this is a significant gap.

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 very short (one sentence), but conciseness is only valuable if the content is sufficient. Here, it is under-specified, so it does not earn full marks. It is not verbose, but it lacks substance.

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 has 3 parameters with no descriptions, no output schema, and no behavioral disclosure, the description fails to provide a complete picture. It is inadequate for an agent to use the tool reliably.

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 descriptions coverage is 0%, and the description does not explain any of the three parameters (target, address, thread_id). The agent has no way to understand what these parameters mean or how to use them correctly.

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?

Description is essentially a tautology: 'Call Stalker.invalidate().' It restates the tool name without explaining what 'invalidate' does or how it differs from sibling tools like frida_stalker_coverage or frida_stalker_configure. The purpose is vague, lacking specific verb and resource clarification.

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. No context on prerequisites, scenarios, or when not to use it. The description does not help the agent decide between this and other tool calls.

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