search_civic_documents

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

No annotations exist, so description must disclose behavior. It only states basic operation and optional filters, omitting details like pagination (limit param), result format, error handling, or rate limits. Fails to provide expected behavioral traits.

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 sentence, 13 words, no redundancy. Front-loaded action and then optional filters. Very concise, though could benefit from listing filters if more detail needed. No wasted words.

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 7 parameters, 100% undocumented in schema, and no output schema, the description is too minimal. It doesn't explain what the search returns, how results are ordered, or timeouts. A search tool requires more context for correct usage.

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?

Description maps 'date range' to from/to and lists filters (jurisdiction, kind, source), adding some meaning. But with 0% schema coverage, it should explain each parameter's valid values or constraints (e.g., no enums for jurisdiction/kinds/sources). Incomplete but partially helpful.

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?

Clearly states it searches state civic documents (bills) by title, differentiating from siblings like get_bill (retrieves single bill) and recent_bills (lists recent). The verb 'search' and resource 'civic documents/bills' are specific.

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?

Mentions optional filters (jurisdiction, kind, source, date range), giving context on when to apply them. Lacks explicit when-not or alternatives like 'use get_bill for a specific bill ID', but the context is clear enough.

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