modify_smali_file

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Modify' implies mutation, but it doesn't disclose whether this overwrites the entire file or allows partial edits, what happens on failure, or if there are validation constraints. The backup parameter hint is useful but insufficient for a mutation tool with zero annotation coverage.

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, direct sentence with zero wasted words. It's perfectly front-loaded with the core action and resource, making it immediately scannable and efficient. Every word earns its place in conveying the essential purpose.

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?

For a mutation tool with 4 parameters, 0% schema coverage, no annotations, and siblings offering related operations, the description is inadequate. While an output schema exists (which helps), the description doesn't address critical context like file format expectations, error conditions, or how modifications interact with the APK building process. It leaves too many gaps for safe, effective use.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'class_name' represents in smali context, what format 'new_content' should be in, or what 'project_dir' expects. The description fails to provide meaning beyond the bare schema, leaving parameters largely unexplained.

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 ('Modify') and resource ('content of a specific smali file'), making the purpose immediately understandable. It distinguishes from siblings like 'get_smali_file' (read) and 'modify_resource_file' (different resource type). However, it doesn't specify what kind of modifications are possible or the scope of changes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a decoded APK), differentiate from 'modify_resource_file' for non-smali modifications, or specify when to use 'create_backup' parameter. The agent must infer usage from context alone.

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