reading_import_book

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

No annotations are provided (only a title), so the description carries the full burden. It states 'Import' which implies a write operation, but it does not disclose side effects (e.g., overwriting existing books), error conditions, or any behavioral details beyond the basic action. For a tool with no annotations, more transparency is needed.

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, directly states the purpose, and front-loads the key information. Every word is necessary and there is no redundant content.

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 has 10 parameters, no output schema, and no behavioral annotations, the description is severely lacking. It does not explain return values, error handling, or parameter details. The agent would have to rely solely on the schema, which for a complex import operation 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?

The input schema has 10 parameters (2 required) but the schema description coverage is 0%. The description only mentions 'base64 content' and 'EPUB or TXT file', providing no explanation for the other parameters such as title, author, format, maxChars, overwrite, etc. The description fails to add 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 verb 'import', the resource 'one EPUB or TXT file', and the method 'from base64 content'. It also hints at the distinction from sibling tools by specifying 'for files small enough for one MCP request', which implies that larger files should use the import_begin/part/finish sequence.

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 explicitly advises when to use this tool: for files small enough for one MCP request. This implicitly tells the agent to avoid it for larger files and provides context for selecting among siblings. However, it does not mention prerequisites or explicitly state when not to use it.

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