get_smali_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get content') but lacks details on permissions, error handling, or output format. While an output schema exists, the description doesn't hint at behavioral traits like whether it's read-only or has side effects, leaving significant gaps.

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 waste—it states the purpose efficiently without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse 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?

Given the tool's moderate complexity (2 required parameters) and the presence of an output schema, the description is minimally adequate but incomplete. It covers the basic action but lacks context on usage, behavioral details, and full parameter semantics, which are needed for effective tool selection.

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 description mentions 'by class name', which maps to the 'class_name' parameter, adding some meaning beyond the schema's 0% coverage. However, it doesn't explain the 'project_dir' parameter or provide context like expected formats or constraints, leaving half the parameters inadequately described.

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 verb ('Get content') and resource ('a specific smali file by class name'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like 'list_smali_files' or 'search_in_files', but the specificity of retrieving content for a single file is reasonably implied.

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. For example, it doesn't mention when to choose this over 'list_smali_files' for browsing or 'search_in_files' for content searching, nor does it specify prerequisites like needing a decoded project.

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