search_federal_register

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

No annotations provided and the description offers no behavioral traits beyond the basic purpose. It does not disclose results format, pagination, or restrictions, which is insufficient for a search tool.

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 extremely concise (one sentence) but at the expense of necessary detail. It lacks structure and omits critical information, making it under-specified rather than efficiently communicative.

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 absence of annotations and parameter explanations, the description is severely incomplete. It does not cover return values, pagination, or how this tool differs from sibling search tools, leaving agents poorly informed.

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 0% and the description does not explain the 'query' or 'limit' parameters. Only a vague hint of 'full-text term' is given, failing to add meaning 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 the tool searches Federal Register documents by full-text term, using a specific verb and resource, and distinguishes from sibling tools that search other data sources.

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 guidance on when to use this tool versus alternatives like search_congress_bills. The description does not mention exclusions or prerequisites, leaving the agent without usage context.

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