lepton_apk_info

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

With no annotations, the description must disclose behavioral traits. It only says 'run... extractor' without explaining side effects, permissions, output format, or whether the operation is read-only. This is insufficient for safe invocation.

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 one sentence and under-specified. While short, it sacrifices clarity for brevity. Important context is missing, making it not genuinely concise.

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 5 parameters, no annotations, and 0% schema coverage, the description fails to provide adequate context. Although an output schema exists, the lack of parameter explanation and behavioral details makes the tool difficult to invoke 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 parameter details. There are 5 parameters (2 required) with no explanation of their meaning, format, or relationship. The 'login' parameter with anyOf null/string is especially unclear.

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 action ('run... apk-info-extractor') and target ('remote APK path'), but does not differentiate from sibling tools like 'inspect_android_apk', which may serve a similar purpose. The verb 'Run' is specific but lacks context about what the extractor does.

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 versus alternatives like 'inspect_android_apk'. The description provides no context about prerequisites, expected inputs, or scenarios.

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