frida_device_get_process

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

With no annotations present, the description must convey behavioral traits. However, it gives no information about side effects, read-only nature, required device state, or return format. The agent gains no insight into what calling this method entails.

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?

While the description is brief, it is under-specified rather than concise. Every sentence should add value, but this single sentence repeats the tool name without providing useful information. It lacks essential context.

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 absence of output schema, annotations, and parameter descriptions, the tool definition is severely incomplete. The description does not compensate for these gaps, leaving the agent unable to determine how to invoke the tool correctly.

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 description coverage is 0%, and the description adds no meaning to 'target' or 'device_id'. The agent has no clues about what values to provide or how they affect behavior, making the schema insufficiently documented.

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 'Call Device.get_process()' is a tautology that merely echoes the function name without explaining what the tool does. While the name suggests retrieving a process, the description fails to clarify the purpose or distinguish it from similar tools like 'frida_device_get_matching' or 'frida_get_device_info'.

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?

There is no guidance on when to use this tool, what prerequisites exist, or how it relates to alternatives. The description provides no context for appropriate usage, leaving the agent without decision-making support.

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