baker_isolate

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

Annotations only declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the description's 'hide all others' adds genuinely useful context: non-listed groups have their visibility changed as a side effect. It still omits whether the hiding is persistent, whether it can be undone, and how the 'baker' target interacts with the group list.

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 front-loaded sentence with zero filler, stating the effect immediately. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere rather than through deliberate tightening.

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?

With two undocumented parameters, no crafted output schema explanation needed but no explanation of what is returned either, and a mutation side effect on unlisted groups, the description is too thin. An agent can guess the intent but cannot confidently supply 'baker' or choose between a string and an array for 'groups'.

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%, so the description must carry the burden of explaining both parameters and does not. It never mentions 'baker' (an integer/string identifier of unclear meaning), nor clarifies that 'groups' accepts either a single string or an array of strings, which is the main ambiguity an agent would hit.

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 states a specific operation on a specific resource: show the listed bake groups and hide every other one, which is exactly what 'isolate' means. It is clear enough to distinguish from a plain visibility toggle, though it never names the adjacent tools (baker_set_visible, baker_set_settings) or explains what a 'bake group' is.

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 guidance on when to choose isolate over baker_set_visible or baker_set_settings, and no prerequisites or caveats are given. The usage is only inferable from the effect statement, and nothing tells the agent what state it must be in beforehand.

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