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

Read-only behavior is already covered by readOnlyHint=true; the description adds useful behavioral details such as returning full text, indicating whether a chunk was cited, and ordering results by score descending. No contradictions with annotations.

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?

Two compact sentences with a front-loaded purpose, a precise return-field list, workflow guidance, and ordering information. Every clause earns its place.

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 one-parameter read-only tool with an output schema, this covers purpose, workflow position, return content, and ordering. An agent has enough information to select and invoke the tool correctly.

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 description clarifies that the tool operates 'for a single chat request' and tells the agent to call it after read_session_detail, indicating where the chat_request_id comes from. Although it doesn't discuss the parameter by name, the single self-describing UUID parameter is sufficiently contextualized.

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 the full document chunks retrieved for a single chat request.' Lists the exact returned fields and names the QA/SA context, making it clearly distinct from siblings like read_chat_request_tool_calls.

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 says to use this after read_session_detail, establishing the correct workflow. It does not enumerate alternatives or when-not conditions, but the intended context is clear and useful.

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