get_current_theme

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, local read. The word 'currently active' adds a little context about what state is reported. Beyond that the description says nothing extra, and because there is no output schema it could have said more about what comes back.

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 well-formed sentence with the key qualifier 'currently active' placed before the resource. No filler.

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?

A zero-param read getter is a simple tool, and the description plus annotations cover the essentials. It would be stronger if it confirmed the return type, since no output schema exists to define it.

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?

There are no parameters, so the schema needs no explanation. The description correctly treats this as a no-argument call.

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 specific verb and resource: 'Get the currently active HyDE theme name'. That is enough to tell it apart from sibling setters like set_theme and next_theme. It does not, however, draw an explicit boundary against sibling getters such as list_theme_wallpapers or get_wallbash_mode.

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 implies read usage but never says when to call this instead of list_themes or next_theme. For a zero-parameter read-only getter the intended use is fairly obvious, which keeps it at minimum viable rather than misleading.

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