iyke_claude_asset_unpin

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

No annotations are provided, so the description carries the full burden. It mentions the fallback rule, but does not disclose side effects, auth requirements, or behavior when the pin does not exist. The description is adequate but not rich.

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, minimal fluff. The key information is front-loaded: action and fallback. Every sentence is useful.

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?

For a tool with three required parameters and no output schema, the description is minimal. It lacks details on return values, error handling, or what happens if the pin does not exist. It is adequate for a simple operation but incomplete for full autonomy.

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 the description adds no meaning to the three parameters (scope, asset_kind, asset_name). It does not explain their roles, constraints, or the enum values, leaving the agent with no additional insight beyond the schema.

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 clearly states the action: 'Remove a pinned resolution.' It also distinguishes from sibling tools like iyke_claude_asset_pin (pin) and iyke_claude_asset_list_pins (list) by its specific verb and resource. The fallback behavior adds clarity.

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?

The context of unpinning is clear, but no explicit when-to-use or when-not-to-use guidance is provided. The description implies usage by naming the action, but lacks exclusions or alternatives beyond the sibling names.

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