get_hda_section_content

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

With no structured annotations, the description carries the full burden and does well: it discloses READ_ONLY safety, explicit encoding modes (utf8/base64), and the internal use of binaryContents() as the authoritative raw byte source for pagination. It also notes the response passes through apply_response_cap, giving the agent a clearer model of behavior.

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 compact and front-loaded with the primary purpose. Every sentence adds value: the encoding constraint, the pagination truth source, and the response cap handling. No filler or redundant text.

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 description adequately explains core behavior but has clear gaps: it does not describe the return format (no output schema), parameter semantics for offset/limit, or any error/edge cases. For a tool with 5 parameters and no structured annotations, more detail would be needed to be fully complete.

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% and the description only meaningfully explains the 'encoding' parameter (utf8/base64 and its relationship to binaryContents). The remaining parameters (limit, offset, section, node_type) are left undocumented beyond their names and types, so the description does not compensate for the schema gap.

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 opens with '分页读取 section 正文' (paged reading of section content), which clearly identifies the verb (read), resource (section content), and unique pagination aspect. It distinguishes itself from sibling tools like set_hda_section_content (write operation) and get_hda_sections (list sections).

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 implies usage by stating 'paged reading of section body' and marks it as READ_ONLY, which helps an agent understand it is for reading content. However, it does not explicitly mention when to choose this tool over alternatives or provide exclusionary guidance, so it relies on the tool name and sibling context.

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