analyze_rung

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

Annotations already declare readOnlyHint=true and openWorldHint=false, establishing a safe read operation. The description adds value by specifying the outputs (structured mnemonic, boolean AST, reads/writes, stateful writes, timers and counters), giving a clearer picture of what the tool returns beyond the annotation flags.

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 a single, focused sentence that front-loads the action ('Parse one rung') and efficiently enumerates the output categories. No wasted words.

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 exists, so return values need not be fully described. The description names the key output categories. It could mention potential error cases or prerequisites, but for a read-only analysis tool with an output schema, this is adequately 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 does not mention any parameters. The parameter names (project_id, program_name, section_name, rung_index) are self-explanatory, but the description provides no additional meaning or compensation for the lack of schema 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 uses a specific verb ('Parse') and resource ('one rung'), and lists concrete outputs: structured mnemonic, boolean AST, reads/writes, stateful writes, timers and counters. This clearly distinguishes it from sibling tools like simulate_rung or compile_structured_rung.

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 its usage (when you need to parse a rung's structure) but does not explicitly state when to use it over alternatives or provide exclusions. No sibling tools are named, so guidance is only implied.

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