List or read journals

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

Beyond the readOnlyHint/idempotentHint annotations, the description adds genuinely useful behavior: chunked content via maxChars, hasMore/nextOffset handling, media pages returning source addresses, and a warning to never write a partial chunk back. This is substantive behavioral disclosure that annotations alone do not provide.

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 dense but every sentence earns its place: invocation modes are front-loaded, and the pagination warning is critical. No filler or repetition.

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?

For a tool with no output schema and several optional parameters, the description covers the main return behavior, media content behavior, and pagination protocol. It relies on the schema for filterQuests/includeContent and does not spell out the exact response envelope, but enough is present for correct invocation.

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 already documents all parameters at 100% coverage, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining how journalId/pageId select different response shapes and how offset/maxChars interact with chunked output.

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 a specific verb (list/read) and resource (journals), and distinguishes three invocation modes by presence of journalId and pageId. It does not explicitly name a sibling like search-journals, so it stops just short of full sibling differentiation.

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 gives clear contextual conditions for each mode ('Without journalId...', 'With journalId...'), which implies when this tool is appropriate. It does not explicitly say when to prefer search-journals or other journal tools, so usage guidance is helpful but not fully explicit.

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