get_reading_journal

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

No annotations are provided, and the description uses 'Fetch' implying read-only behavior, but it does not explicitly state whether the operation mutates data, access restrictions, or other behavioral traits with the detail 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 concise sentences, front-loaded with the main purpose, and includes relevant details without unnecessary 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?

Given the tool's simplicity (4 optional parameters, no output schema), the description covers key aspects (purpose, data types, filters) but lacks sorting or default order information.

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% and the description summarizes parameters as 'optional filters', adding minimal extra meaning beyond the explicit schema descriptions.

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 'fetch' and the resource 'reading journal entries' for the authenticated user, listing included data types (notes, quotes, etc.), which distinguishes it from sibling tools like get_book or get_user_library.

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 optional filters for query context but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare to siblings like add_journal_entry or delete_journal_entry.

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