configure_library_provider

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

No annotations provided, so description carries full burden. It describes the action but does not disclose whether reconfiguring overwrites existing settings, destroys previous data, or requires specific permissions. The note about Mendeley's BibTeX usage adds some behavioral context.

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 front-loaded with the main purpose, followed by usage timing, then a clear parameter block. Each sentence adds value without redundancy. Well-structured and 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?

Output schema exists but its content is unknown; description does not mention return values, success/failure indicators, or error handling (e.g., invalid API key). For a configuration tool, agent might need to know what happens on success or if changes are immediately applied.

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 compensates fully by explaining each parameter: provider options ('zotero' or 'mendeley'), source for api_key and user_id, and bibtex_path purpose for Mendeley. This adds significant meaning beyond the bare schema.

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 configures the library provider for the Metis installation and is used during setup or when switching reference managers. This distinguishes it from sibling tools like sync_zotero_library or import_bibtex_library which handle data syncing/importing.

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 says 'Call this during setup or when switching reference managers' providing clear context. Notes that Mendeley uses BibTeX export. Does not mention when not to use, but the use case is well-defined.

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