Read a U.S. Code section

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

Goes well beyond the safety annotations (readOnly/idempotent/openWorld) by disclosing that output is paginated character-bounded pages, that it reflects the published OLRC release rather than real-time amendments, that the service is a non-government mirror, and that retrieved text should be treated as data rather than instructions (an explicit injection defense).

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?

Front-loaded purpose in the first clause, then pagination, citation, and provenance requirements in descending priority. Dense but every sentence carries an operational rule; the citation-formatting and disclaimer sentences are long but necessary, with no redundant restatement.

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?

With an output schema present, the description needn't describe return fields like inlineCitation or nextOffset in detail, and it correctly focuses on provenance, pagination loop termination, and citation obligations. The only shortfall is that length/offset input semantics are left unexplained, which matters for paging a long 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%, so the description carries the burden: it does explain the path format and gives a concrete example, and it implies offset behavior via 'follow nextOffset until null'. However, the 'length' parameter (page size, max 60000) is never named or characterized, and 'offset' is never explicitly defined as a character offset, leaving a real gap for a 3-param tool.

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 a specific verb+resource ('Retrieve full statutory section text') and the exact addressing mechanism ('canonical path returned by search, e.g. /title/5/section/552'), which cleanly separates it from search_uscode (snippets) and list_titles (title enumeration).

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?

Explicitly routes the agent: 'Retrieve section text before quoting a search snippet' names the alternative tool's output and the condition that mandates this one. It also gives the iteration rule ('follow nextOffset until null for the full section') and the citation/currency conditions under which the returned metadata must be surfaced.

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