get_hda_section_content

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

With no annotations, the description carries the full behavioral burden. 'Read' implies a safe, non-mutating operation, but the description says nothing about what happens if the node_path or section_name is invalid, what format the content is returned in, or whether large sections are truncated.

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 single purpose sentence is appropriately front-loaded and short, but it is padded with auto-generated 'Args: ctx: MCP context' boilerplate that contributes nothing for an agent.

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 tool with no annotations, no output schema, and 0% parameter coverage, the description is too thin. An agent cannot tell how to obtain valid section names, what the return value looks like, or how errors are surfaced.

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 0%, so the description must compensate for both parameters. Instead it only restates the field names ('node_path: Node path', 'section_name: Section name'), adding no format, example, or constraint information (e.g., valid section names or path syntax).

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 states a specific verb and resource: 'Read the content of a specific section in an HDA definition.' This distinguishes it from the mutating sibling set_hda_section_content and complements get_hda_sections, though it does not name those siblings explicitly.

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 guidance on when to use this tool versus get_hda_sections (to discover section names) or get_hda_info. No prerequisites, exclusions, or workflow context are given.

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