frida_sqlite_exec

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

With no annotations, the description bears full burden. It only states the basic action and lists parameters, but does not disclose return values, side effects (e.g., database mutability), error handling, or permissions needed. This is insufficient for safe usage.

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?

Extremely concise: one sentence for purpose, followed by three parameter definitions. Front-loaded and no wasted words. Every part earns its place.

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 an operation that executes arbitrary SQL, the description is incomplete. It omits return format, transaction behavior, async behavior, and error states. Siblings like frida_sqlite_open suggest prerequisites, but this is not addressed. Inadequate for safe usage.

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 description adds meaning to each parameter (target as process name/pid, db_path as file path, sql as statement) beyond the schema's mere titles. With 0% schema coverage, this is valuable, though more detail (e.g., SQL dialect) would improve.

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 tool executes SQL against a SQLite database inside the target process, using a specific verb and resource. It distinguishes from related SQLite tools (like dump/open) by focusing on arbitrary execution, but does not explicitly differentiate.

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 vs. alternatives like frida_sqlite_dump or prerequisites (e.g., database must be open). The agent is left without context for appropriate invocation.

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