iyke_claude_asset_list_pins

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

No annotations provided, so description carries full burden. Discloses return structure (preferred_tier + preferred_source) and scope semantics. Lacks details on side effects, idempotency, authentication, or error behavior.

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, front-loaded with main action, no extraneous information. Every word contributes to understanding.

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 schema (1 required param, no output schema), description adequately covers return format and scope options. Minor gaps: no mention of pagination, empty list behavior, or rate limits, but these are typical for a list tool.

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 has 100% coverage on the only parameter 'scope'. Description adds context beyond schema by explaining the two scope literals and the return fields, adding value for agent decision-making.

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 'List', resource 'Claude-config asset pins', and scope options ('workspace' or 'project:<id>'). Differentiates from sibling tools like 'iyke_claude_asset_pin' and 'iyke_claude_assets_list' by focusing on pins specifically.

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?

Describes valid scope values and what the tool returns. Clear context for use but lacks explicit when-not-to-use or alternatives (e.g., no mention of when to use iyke_claude_asset_pin instead).

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