delimit_design_component_library

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

The description discloses that it is a read-only scan with no writes, and mentions the backend used. Since no annotations are provided, this is crucial. However, it does not detail the exact return format beyond "catalog" or mention any performance/error behavior. Still, it is sufficiently transparent for a scanning tool.

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?

The description is very concise and well-structured with four short, clear sections: main action, when to use, when not to use, sibling contrast, and side effects. Every sentence adds value without redundancy.

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 the presence of an output schema, the description does not need to explain return values. It adequately covers purpose, usage, side effects, and sibling differentiation. The only minor gap is not specifying file extension or prerequisites, but it is overall complete for this tool's complexity.

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 100%, so the input schema already fully describes both parameters (project_path and output_format). The tool description does not add any extra semantic meaning beyond what is in the schema, so it meets the baseline of 3.

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 it scans a project for React/Vue/Svelte components and emits a catalog, which is a specific verb and resource. It distinguishes from siblings like delimit_design_generate_component (which creates one component) and delimit_story_generate (which generates stories).

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 provides when to use (inventory UI components for review, docs, design-system curation) and when NOT to use (to generate a single component or stories). Also names specific sibling alternatives, offering clear guidance on tool selection.

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