readwise_action

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

With no annotations and a bare description, behavioral aspects like authentication, rate limits, side effects (e.g., creation of highlights), or error modes are not disclosed. The description only enumerates actions.

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 extremely concise (one sentence), which is efficient but lacks necessary structure for a multi-action tool; it does not separate or explain each action's requirements.

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?

No output schema, no annotations, and no description of return values or error handling. For a tool supporting multiple sub-actions, this is insufficient.

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 has 6 parameters with 0% description coverage. The description adds no meaning to parameters beyond listing 'action' implicitly. For example, 'api_key' or 'book_id' are unexplained.

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 lists possible actions but does not define a clear, specific purpose for the tool itself; 'Perform a Readwise action' is vague. It fails to differentiate from sibling tools, which are unrelated.

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?

No guidance is provided on when to use this tool vs alternatives, which actions exist for what context, or prerequisites. The agent is left guessing.

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