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

The description adds real behavioral context beyond the annotations: a required Authorization bearer key, a metered read that 'Consumes one available read', and the clarification that budget/token estimates are approximate costs rather than billing. This also explains why readOnlyHint=false despite the 'Read' verb (quota side effect), so no contradiction arises.

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?

Four tight sentences, front-loaded with the core action and followed by auth, cost, and pagination notes. No filler, though the wording is dense enough that the param mapping is easy to miss.

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?

Auth, quota consumption, and budget semantics are covered, which suits a tool with no output schema. However, the q, id, and exact cursor/budget parameter meanings remain undocumented in both the schema and the description, leaving key invocation details incomplete.

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 description coverage is 0%, so the description must carry all parameter meaning. It hints at 'budget' (maxChars) and 'nextCursor requests another excerpt' (cursor), but never names the parameters precisely and leaves both 'q' and 'id' entirely unexplained, which is a serious gap for a required id.

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: 'Read selected evidence within a JSON character budget.' An agent can distinguish this as a retrieval call from siblings like search_research, though the description never explicitly names those alternatives to sharpen the contrast.

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?

There is no explicit when-to-use guidance or routing versus search_research, prepare_contribution, or other siblings. The note that it 'Consumes one available read' implies a metered context but stops short of telling the agent when this tool is the right choice.

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