frida_module_find_global_export_by_name

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

With no annotations, the description must describe behavior. It only states the API call, omitting side effects, permissions, error conditions, or return values. This is insufficient for safe and effective use.

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 sentence, but it is under-specified rather than concise. It lacks structure and fails to convey essential information, making it unhelpful.

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 complexity of Frida tools, the absence of annotations and output schema, and the large set of sibling tools, the description is entirely inadequate. It provides no contextual completeness for correct 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 schema has 0% description coverage, and the description adds no meaning to the parameters 'target' and 'name'. It does not explain what they represent, leaving users to guess.

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 states the underlying GumJS method call but does not explain what the method does. It does not differentiate from sibling tools like frida_find_export_by_name, leaving the purpose ambiguous for users unfamiliar with GumJS.

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 is provided on when to use this tool versus similar alternatives. There is no mention of prerequisites, context, or usage scenarios.

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