bulk_import

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 discloses validation, dedup, agents filling, resource inference, and profile sync. However, it does not mention side effects (e.g., whether source files are modified), authentication needs, or error handling, leaving gaps.

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 a single paragraph with no wasted words. It front-loads the core action and adds details sequentially. Could be slightly improved with bullet points for clarity, but overall efficient.

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 tool complexity (7 params, no output schema, no annotations), the description provides adequate but not complete context. It explains main behavior and a few parameters, but leaves many details about error handling, prerequisites, and return behavior implicit.

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?

With 0% schema description coverage, the description must compensate. It explains source_dir, agents, and verbose, adding meaningful context. However, four parameters (allow_synthesized_frontmatter, sync_profiles, profile_roots, discover_profile_roots) remain unexplained, so coverage is only partial.

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 (import) and resource (immediate child directories containing SKILL.md). It also distinguishes behavior from sibling propose_skill by referencing it, but does not explicitly differentiate from other siblings like add_skill or update_skill.

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 description does not provide explicit guidance on when to use bulk_import versus alternative tools. It mentions 'like propose_skill' but lacks any when-to-use or when-not-to-use instructions, leaving the agent without decision support.

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