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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: the 4,000-character truncation with a flag, the pagination contract (offset/next_offset/has_more), and the embedded instruction to fall back to source_url rather than hallucinate. It also discloses provenance and verification, which is useful trust context for a legal/tax library.

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?

Front-loaded with the core action and return shape, then pagination, then usage context. The provenance sentence and Hebrew title fragment are somewhat extraneous to invocation, but the rest is dense and every sentence carries operational information.

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?

With no output schema, the description carries the burden of describing return values and does so field by field, including truncation and pagination semantics. For a two-parameter read tool with full annotation coverage, nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that offset continues reading and that each call returns up to 4,000 characters, tying offset to the next_offset/has_more loop. doc_id itself is only described as 'Document ID' in both places, so it is not fully compensated.

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?

States a specific verb and resource ('Retrieve a complete MISIM.AI library document by ID') and enumerates the returned fields (title, kind, issuing body, AI summary, body, publication date, source URL). It also names the sibling it follows (misim_search_library), so an agent can distinguish it from the search tools without opening a schema.

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?

Explicitly positions the tool in a workflow: 'Used after misim_search_library to show full document content in context,' and explains the continuation pattern (call again with offset = next_offset while has_more is true). It lacks an explicit when-not or a note on what to do if the doc_id is unknown, but the usage context is clear.

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