fed_register_search_documents

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

No annotations are provided, so the description carries full burden. It only says 'Search' implying read-only but does not disclose rate limits, pagination behavior, default perPage, or any potential side effects. More behavioral context is needed given the lack of annotations.

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?

Two sentences efficiently front-load purpose and include a concrete usage example. No extraneous 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 7 parameters, zero required, and no output schema, the description covers the main search purpose and filter types. However, it does not explain pagination, default values, or return format. Adequate but could be more complete for a tool with many parameters.

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 71% (5 of 7 parameters have descriptions). The description lists filter types (query, agency, type, date range) which aligns with parameters, but adds no meaning beyond the schema. For example, agencySlugs description already tells to use fed_register_list_agencies. Schema already provides enum for type. Thus, minimal added value.

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, explicitly lists document types (proposed rules, final rules, notices, presidential documents), and specifies filter dimensions (query, agency, type, date range). This distinguishes it from siblings like fed_register_get_document and fed_register_list_agencies.

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 provides a concrete usage example ('what new VA cybersecurity rules came out this quarter?') and implicitly guides the agent to use fed_register_list_agencies for agency slug resolution. It does not explicitly state when not to use, but the example gives clear context.

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