chat.read_knowledge_file

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys pagination, read-only nature ('Read'), and file specificity, but does not mention error handling, required permissions, or behavior on invalid runId.

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?

A single concise sentence that front-loads the action ('Read') and resource. No wasted words, clearly structured for quick scanning.

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?

The tool has only 3 simple parameters and no output schema. The description explains it reads paginated text, which is adequate for basic invocation, but lacks details on return format or edge cases and doesn't differentiate from sibling tools.

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%, with all parameters (runId, limit, offset) described in the schema. The description adds context about pagination that maps to limit/offset, but no new semantics beyond the schema. Baseline of 3 applies.

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 'Read paginated text from a specific persisted per-chunk knowledge file' with a specific verb and resource. It distinguishes this from sibling tools like read_knowledge_batch by emphasizing 'specific' and 'per-chunk', though it doesn't explicitly name alternatives.

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?

No explicit guidance is given on when to use this tool versus siblings like read_latest_knowledge or search_knowledge. The description implies use for reading a known file with pagination, but lacks exclusions or alternative recommendations.

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