supershift_reverse_engineering_report

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

With no annotations, the description fully shoulders the burden of disclosing behavioral traits. It only says 'Return the map', but does not mention whether this is read-only, any side effects, authentication needs, or performance implications. The agent cannot infer safety or impact.

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 extremely concise (one sentence), which is good for conciseness, but it omits critical details. It's not well-structured; it lacks any breakdown of purpose, usage, or behavior.

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?

Although an output schema exists (reducing need to explain return values), the description lacks context about input parameters, behavioral traits, and when to invoke this tool. Given the tool's moderate complexity (2 optional parameters), the description is insufficient.

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 input schema has two parameters (jadx_dir, apktool_dir) with zero description coverage. The description adds no meaning to these parameters, leaving the agent to guess their purpose and format.

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 action ('Return') and the resource ('reverse-engineering map for write-capable Supershift paths'), distinguishing it from sibling tools which focus on shifts, device status, etc. However, it could be more specific about what 'write-capable Supershift paths' means.

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 alternatives, such as `preview_supershift_write` or `inspect_supershift_apk`. The agent is given no context about prerequisites or typical use cases.

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