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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: what each node_id depth returns and that omitting year selects the Current edition versus a specific loaded edition. It does not say what happens if a requested year is not loaded.

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?

Three terse clauses, each front-loaded with the highest-value information (what the tool is, then the node_id grammar, then the year switch). No filler or restatement of the title.

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 shape needs no explanation, and the two optional parameters are both addressed. What's missing is edge behavior — invalid node_id, unloaded year, or whether leaf section results duplicate iac_get_section.

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% — the schema only has titles and defaults — so the description must carry the burden, and it does: it enumerates concrete node_id formats at each hierarchy level and explains year's default ('omit it for Current'). The gap is that 'loaded edition' is never defined, so valid year values remain undiscoverable from this text.

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?

States the specific resource (Indiana Administrative Code outline) and, through the four node_id examples, precisely characterizes the tool as a hierarchical walk over titles → articles → rules → sections. That makes the 'browse' verb concrete. It does not explicitly contrast with siblings like iac_get_section or iac_search, though the outline framing implies the distinction.

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?

Gives explicit call patterns: no node_id for titles, '10' for articles, '10-1.5' for rules, '10-1.5-1' for sections, plus the year/Current rule. That is real when-and-how guidance. It stops short of saying when to prefer this over iac_search or iac_get_section.

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