kimo_enable_group

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

With no annotations, the description carries the full burden, and it does disclose two real traits: the change persists ('from now on') and the server emits notifications/tools/list_changed. However, it says nothing about reversibility (is there a disable counterpart?), idempotency, or error behavior for an invalid group name.

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 sentence with the effect front-loaded and the mechanism in a parenthetical; no filler. Slightly terse given the concepts ('group') it assumes the reader already knows.

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 stateful, side-effecting tool with no annotations, no output schema, and an undocumented required parameter. The description should at minimum define what a 'group' is and how its name is obtained, and note whether the setting can be undone.

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 coverage is 0% and the single required 'name' parameter has no description. The description only alludes to 'a group', leaving the agent to guess whether name is a group identifier, a display name, or a path.

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 conveys the effect of enabling a group — its tools are listed individually going forward — but the phrasing 'List every tool of a group individually from now on' reads like an instruction to the agent rather than a description of a stateful toggle, so the verb does not match the name 'enable_group'. It is distinguishable from siblings like search_tools, but only indirectly.

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?

There is no statement of when to use this versus alternatives such as kimo_describe or search_tools, nor any prerequisite or context for calling it. The agent must infer the trigger condition entirely.

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