get_rungs

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

The readOnlyHint annotation already signals a safe read operation, and the description adds useful context by stating that structured=true adds read/write and boolean-expression analysis. This goes beyond the annotation by revealing what enriched information is computed, though the phrase 'read/write analysis' is a bit terse.

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 two short sentences, front-loaded with the core action, and contains no filler or redundant information. Every part contributes to understanding the tool's purpose or optional behavior.

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?

An output schema covers return values and annotations cover safety, so those areas are adequately handled elsewhere. However, with zero parameter descriptions and no guidance on deciding between this tool and related analysis tools, the description is only minimally complete for a tool with five parameters and optional structured behavior.

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 schema has 0% description coverage, yet the description only elaborates on structured, leaving include_empty, project_id, program_name, and section_name without added semantics. The parameter names and titles are somewhat self-explanatory, but the description does not compensate for the schema's lack of descriptions.

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 a specific verb and resource: "Read rungs from one section," which clearly states the core functionality. The phrase "one section" scopes the operation and helps distinguish it from broader tools like list_sections or rung-analysis tools.

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 use when rungs from a single section are needed, but it does not explicitly state when to prefer this tool over alternatives such as analyze_rung or search_program. The structured=true hint gives some usage context, but no exclusions or alternative guidance are provided.

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