pin_window

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

Discloses that pinning a tiled window results in a warning and no effect, which is critical behavioral context beyond the basic function. No annotations provided, so description carries full burden. Could mention potential side effects or prerequisites like workspace context, but sufficient.

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 sentences, no wasted words. Front-loaded with purpose, then constraint and remedy. Every sentence earns its place.

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 zero parameters and no output schema, the description fully covers the tool's function, limitations, and fallback action. No gaps remain for the agent.

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?

No parameters exist (schema coverage 100%), and description adds no parameter-level details. Baseline 4 per guidelines for zero parameters.

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 'Pin the active window so it stays visible across all workspaces' with specific verb (pin) and resource (active window), and implicitly distinguishes from sibling tools like toggle_floating.

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 'Only works on FLOATING windows' and provides alternative: 'Use toggle_floating first if this warns and the window should stay pinned.' This is excellent when-to-use and when-not-to-use guidance.

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