Get a regulation by number

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

The description discloses that it returns full verbatim text and the associated Part. Without annotations, it adequately conveys the read-only behavior, though could mention error handling for invalid numbers.

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?

Single, well-structured sentence of 24 words. Front-loaded with the action and resource, no redundant information.

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?

Given the simplicity and the presence of siblings, the description is sufficient. It explains the return value (full text with Part) but does not detail the 'Part' concept, though that is acceptable for a targeted tool.

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 100%, so the parameter description is already in the schema. The tool description adds context about the 2026 regulations but does not significantly enhance parameter understanding beyond the schema.

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 clearly states it returns the full verbatim text of a numbered regulation (1-34) with its Part. It specifies the range and regulation name, distinguishing it from siblings like list_regulations or get_part.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it or suggest siblings like list_regulations for browsing numbers.

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