fr_search

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

The description discloses return format (snippets with markers, structuredContent.citations) and error codes, adding value beyond annotations which already indicate safe, idempotent, non-destructive behavior. No contradictions.

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, concise sentence with key information front-loaded: search type, domain, output specifics, optional filter, and error codes. No superfluous content.

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 no output schema, the description adequately explains return structure (snippets, citations), error codes, and parameter options. Sibling tools provide complementary context, making this complete for an agent.

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 has 100% coverage; description adds a concrete example for the documents parameter and explains error codes, slightly enhancing understanding beyond the schema alone.

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 performs full-text search (FTS5) over French legal codes and laws, with distinct outputs like snippets and citations. It differentiates from sibling tools like fr_article and fr_list_documents.

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 implies usage for free-text search but lacks explicit guidance on when to use this tool versus alternatives like fr_article for specific articles or fr_list_documents for document listing. No when-not scenarios mentioned.

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