fetch_current_class

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

With no annotations, the description carries the behavioral burden. It usefully discloses that Kotlin compiler metadata is stripped by default and that slim=False yields a raw dump, plus that line numbering is unaffected, but it omits error behavior when no class is selected and any permission or safety context.

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 front-loaded with the tool's purpose and then gives targeted parameter behavior in two short sentences. There is no redundant or wasted phrasing.

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 one-parameter tool with an output schema, the description covers purpose and parameter semantics adequately. It is only slightly incomplete in not clarifying what happens if no class is currently selected in the GUI.

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 for the single slim parameter. It does so clearly by explaining the default stripping behavior and the meaning of slim=False as a raw dump, though it does not detail the exact raw output shape.

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 gives a clear verb and resource: fetch the currently selected class and its code from the JADX-GUI plugin. It distinguishes the tool by emphasizing the current GUI selection, though it does not explicitly contrast this with siblings like get_class_source or get_selected_text.

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?

Usage is implied by 'currently selected class,' and the description explains how to get a raw dump with slim=False. However, it does not state when to use this tool instead of related siblings such as get_class_source or get_selected_text.

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