skill_import_file

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

Adds beyond annotations by stating the save location (library/) and sandbox path constraint. Annotations indicate mutability, and description clarifies scope without contradicting them.

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?

Three sentences with clear front-loading of purpose, followed by constraint and preference. No redundant information.

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?

Covers purpose, constraints, and preference. Output schema exists for return values, so description is sufficient for an import tool, though could mention result behavior.

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 baseline is 3. Description adds extra meaning by noting the sandbox restriction and ownership requirement, which are not fully captured in schema descriptions.

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 specifies the verb 'build' and resource 'L4 skill package from a local book file', clearly distinguishing it from the sibling tool `skill_import_url` which imports from a URL.

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 explicit when-to-use (local file import) and a requirement (ownership_attested for user_owned), but does not explicitly mention when not to use or alternatives like `skill_import_url`.

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