frida_enumerate_ranges

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

The description explains the behavior: enumerates ranges, protection matching is superset, returns base, size, protection, backing file. However, it does not explicitly state that the operation is read-only or safe, and no annotations are provided to compensate.

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, with a clear purpose statement followed by parameter clarification. No extraneous information; can be read quickly.

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?

The description covers purpose, parameters, and return data adequately for the tool's complexity (2 params, no output schema). It is sufficient for an agent to invoke correctly, though an example return could enhance completeness.

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%, so the description must add meaning. It explains 'target' as process name/pid and 'protection' as filter with examples and superset matching, plus default value. This goes beyond the bare 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 the tool enumerates memory ranges matching a protection filter, which is a specific verb-resource pair. It distinguishes from sibling tools like frida_enumerate_modules or frida_enumerate_sections.

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 explicit guidance on when to use this tool versus alternatives or when not to use it. The description implies usage for filtering memory ranges by protection, but lacks exclusions or context.

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