remove_library_item

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

No annotations provided, so the description must carry full behavioral disclosure. It explains the default (file left untouched), the safety guard for delete_file (only paths inside PKM root), and the return value (confirmation or error message). This is comprehensive for a mutation 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 concise: a one-sentence summary followed by details in a structured Args/Returns format. Every sentence adds value without redundancy. It is front-loaded with the core action.

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 complexity of the operation (index removal with optional file deletion) and no annotations, the description covers purpose, usage, parameters, and return value well. A minor gap is the lack of explanation of 'PKM root' or 'Metis index' but these may be understood from broader context. Overall, it is largely complete.

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 description coverage is 0%, but the description adds full meaning: relative_path is the primary key for the library_seeded table, delete_file behavior and default, and the within-PKM-root safety check. This compensates entirely for the lack of 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 clearly states 'Remove a library item from the Metis index' with the verb 'remove' and resource 'library item'. It distinguishes from sibling tool archive_library_item by noting the alternative for hiding rather than removing. The purpose is specific and differentiated.

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 explicitly says 'To hide rather than remove an item, use archive_library_item instead,' providing clear when-not and alternative. It also explains the default behavior (index-only removal) and when to set delete_file=True, with a safety guard noted.

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