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

The annotations already declare idempotentHint=true and destructiveHint=true, so the sentence about repeated calls yielding the same result largely restates structured data. The description does add the pipeline-board effect, but it never explains the destructiveHint=true flag or what an unpin removes from a user's view, which is the most consequential behavior here.

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 short sentences with the core action front-loaded, which is easy to scan. The second sentence is largely redundant with idempotentHint and could have been replaced by parameter guidance.

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?

There is no output schema and no schema descriptions, so the description is the only place parameter meaning and side effects could be conveyed. It covers the board-level effect adequately for a simple toggle but leaves the destructive behavior and the boolean's polarity unexplained.

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 description coverage is 0% and both parameters are nested, yet the description never maps 'pinned' to pin/unpin or explains that dealId identifies the target deal. The title implies a boolean toggle but the body provides no compensating semantics for either parameter.

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 verb and resource ('Pins or unpins a deal') plus its scope ('on the deal pipeline board'), which lets an agent distinguish it from nearby tools like updateDeal, moveDeal, and pinContact. It stops short of naming a sibling for contrast, so it sits just below a 5.

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 pin versus when to use updateDeal's fields or moveDeal, and no mention of prerequisites such as deal existence or pipeline membership. The agent must infer usage entirely from the tool name.

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