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

With no annotations, the description carries the full behavioral burden. It does disclose that the data is 'certified (human-reviewed)', that there is no API key required, and that all parameters are optional/combinable. However, it does not disclose return format, pagination behavior (how limit/offset work), what happens when no params are supplied, or any rate limits. It adds some context beyond the schema (source quality, free access) but leaves material behavioral gaps.

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 two sentences with zero waste. The first sentence front-loads the exact purpose and domain, and the second adds the two most important operational facts (free/no key, all params optional). Every word serves a purpose.

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 9 optional parameters, no output schema, and no annotations, this description is not complete enough for an agent to use the tool correctly. It tells the agent what the tool searches and that all params are optional, but it does not explain what each parameter does, how to construct a meaningful query, what the response looks like, or whether there are default limits/pagination. An agent would be guessing at the meaning of tag, subject, status, etc.

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 very low (11% — only 'q' is documented). The description compensates only by stating 'All params optional and combinable' and by defining the domain of the records, which hints at what tag/state/topic/carrier might mean. It does not explain any of the eight undocumented parameters, nor provide examples of how to combine them. With such low schema coverage, the description needed to do much more to make the parameters self-explanatory.

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 states a specific verb ('Search'), a named resource ('Skyline's certified (human-reviewed) records'), and scopes it to three clear domains (Oklahoma property insurance, roofing regulation, insurance-industry news). This distinguishes it from siblings like get_record or list_changes_since, which are clearly retrieval/history tools rather than full-text search.

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 gives practical context: 'All params optional and combinable' and 'Free — no API key required.' However, it does not explicitly state when to use this tool versus alternatives like get_record (e.g., when you need keyword search vs. when you have a record ID). Usage is implied by the 'Search' verb, but with no exclusions or alternative routing, it stops at 'clear context, no exclusions' and lacks the 'when-not' guidance that would earn a 4.

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