index_bookmarks

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

With no annotations, the description carries the full burden. It discloses that indexing goes into a local SQLite FTS5 database and mentions offline determinism, but does not explain key behaviors like whether indexing is idempotent, what happens on re-indexing, or if fetchPublic requires network access. This leaves significant gaps for a 7-parameter 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?

Two sentences, front-loaded with the core purpose. Efficient with no wasted words, though it could be slightly expanded to cover key parameters without losing conciseness.

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 7 parameters, no output schema, and no annotations, the description is highly incomplete. It does not explain return values (what does indexing return?), parameter constraints, or provide any usage context. The agent would be underinformed for correct invocation.

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 0%, so the description must compensate. It only hints at the 'offlineOnly' parameter via the offline mode mention, but fails to explain 'filePath', 'force', 'limit', 'dbPath', 'folder', or 'fetchPublic'. The agent gains almost no additional meaning beyond the 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 action (index) and resource (bookmark metadata/content) into a specific target (local SQLite FTS5 database). However, it does not differentiate from sibling tools like 'search_bookmarks_fulltext' which might rely on the indexed data.

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 mentions offline mode being deterministic and network-free by default, hinting at a use case, but it does not explicitly state when to use this tool versus alternatives like 'search_bookmarks_fulltext' or 'get_bookmark_content'. No exclusion or prerequisite guidance is given.

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