iyke_layout_reset

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

No annotations provided; description fully carries burden. Discloses that the tool deletes state and leaves current view in place. Lacks mention of auth or error scenarios, but sufficient for the action.

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?

Two efficient sentences, front-loaded with action and consequences. No extraneous information.

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?

Given simple destructive action with one parameter and no output schema, description covers purpose, effect, and use cases adequately. Missing parameter documentation reduces completeness slightly.

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?

Single parameter 'project_id' has 0% schema description coverage. Description adds no explanation of the parameter, relying on the name alone. Should clarify expected value.

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?

Description clearly states verb 'Reset' and resource 'project's saved layout', enumerates specific items deleted (pane tree, files-explorer state, panel sizes), and is distinct from sibling tools like iyke_layout_get.

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?

Explicitly states when to use: 'recover from a wedged layout' or 'clean-slate workflow'. Does not provide explicit exclusions but context is clear enough.

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