sync_readwise

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

Annotations indicate readOnlyHint=false and idempotentHint=false, which the description supports by describing a write operation (import) and two modes with different idempotency characteristics (incremental may be idempotent, full is not). The description adds behavioral details about modes beyond annotations, but does not elaborate on side effects like duplication or rate limits.

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 two sentences long, front-loading the primary action and then efficiently covering modes and prerequisite. Every sentence adds essential information with no fluff.

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 tool's simplicity (1 parameter, has output schema), the description covers purpose, usage, and prerequisite. Missing details about error handling or what happens if not connected, but these are minor omissions for a straightforward import tool.

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%: the input schema fully describes the 'mode' parameter with enum, default, and description. The tool description repeats the mode options but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 ('Import highlights from your Readwise library into your BrainTube corpus'), specifies the resource (highlights), and distinguishes the tool from siblings by mentioning the prerequisite connect_readwise. The verb 'import' and the target 'BrainTube corpus' are specific and unambiguous.

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 provides explicit guidance on when to use each mode ('incremental' for new highlights, 'full' for re-import), including the default. It also notes the prerequisite 'Requires connect_readwise first.' However, it does not explicitly contrast with alternatives or state when not to use the tool.

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