set_favorite

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

Discloses all behavioral traits: idempotent (same value no-op), persists to local SQLite, no external auth/rate limits, returns `{success: true}`. No annotations exist, so description carries full burden and meets it.

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: first defines action and key behavior (idempotent/not toggle), second covers persistence/return/auth, third gives use case and related tools. No wasted words.

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?

Fully covers all needed context: input (2 params with types and behavior), output (success object), preconditions (idempotent), side effects (SQLite), and related tools. No gaps.

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 3. Description adds meaning beyond schema by clarifying file_id is a file and favorite is desired state (not toggle). Justifies above baseline.

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?

Description clearly states 'set or clear the favorite flag on one file' with specific verb and resource. Distinguishes from sibling tools like list_files and search by noting how they use the favorite filter.

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 states when to use ('curate quick-access pins') and what not to do ('not a toggle'). Mentions alternative tools (list_files/search with filter) for retrieval.

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