Fetch Current Class

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

No annotations are provided, so the description carries the full burden; it does at least indicate this is a read of the active selection and that code is returned. It is silent on the important edge case of no current selection (error vs. empty result) and on whether it depends on GUI focus/state, which matters for a selection-scoped tool.

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?

A single short sentence with the scope qualifier ('currently selected') front-loaded and no filler. Nothing is wasted.

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?

An output schema exists, so return values need not be explained, and a zero-parameter read tool needs little more than a clear statement of what it fetches. The only meaningful omission is behavior when no class is selected, which slightly weakens completeness.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made that could mislead.

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?

States a specific verb (fetch) and a specific resource (the currently selected class plus its code) tied to the JADX-GUI plugin. It is largely distinguishable from siblings like get_all_classes or get_class_source, though the overlap with get_selected_text and get_class_source (which also returns a class's code) is not addressed.

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 phrase 'currently selected' implies the use case (work from whatever the user has open rather than naming a class), but there is no explicit when-to-use/when-not guidance or named alternative. An agent must infer that this is the tool for the active GUI selection versus 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.