iyke_claude_assets_list

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

With no annotations, the description carries full burden. It explains that the output is a tree showing conflicts between tiers, and that it defaults to the active project. Good behavioral context beyond a simple 'list'.

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?

Four sentences, each serving a distinct purpose: action, output format, defaults/parameter, usage advice. No fluff, front-loaded.

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?

Explains return value structure (tree with AssetSource entries and conflict indication). Lists asset kinds covered. Lacks details on error scenarios or access restrictions, but given no output schema and 0 required params, coverage is reasonable.

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 coverage is 50% (kind described, project_id not). Description adds meaning: kind filters to one asset kind, project_id queries a specific project. Could be more explicit about project_id format (likely a string ID).

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 tool lists Claude-config assets (skills, agents, commands, hooks, mcps) discovered for a project, grouped by provider tier. It distinguishes from sibling tools like iyke_claude_asset_list_pins by focusing on discovered assets rather than pinned ones.

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?

Provides clear usage context: 'Use this to see what an agent will actually load in a project context.' Mentions defaulting to active project and ability to specify a project_id. Does not explicitly state when not to use or list alternatives, but the context is sufficient.

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