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

With no annotations, the description carries the full behavioral burden and mostly fails: it never says the call is read-only, what is returned, or how billing works beyond the cryptic "UNKNOWN never charged" remark. The freshness stamp ("data as of 2026-10-26") and the billing hint add a little real context, which keeps this above a 1.

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?

It is short but the entire sentence is marketing and metadata rather than operational information. Every clause is about vendor credibility, not about how to invoke the tool, so brevity here reflects under-specification rather than efficiency.

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?

For a tool with no annotations, no output schema, and 0% parameter documentation, the description should supply purpose, usage, and parameter meaning; it supplies none of these. Only the accuracy/uptime claims and a date are present.

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% for two parameters (jurisdiction, limit), and the description adds no meaning to either. An agent gets no clue about jurisdiction format (state? county? FIPS?) or what limit constrains.

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 never states what the tool does. It consists entirely of trust metrics ("100% golden accuracy (78/78)", "100% page-cited", "100% uptime") and a data timestamp. Only the name get_recent_decisions hints at retrieving recent decisions, and the domain (legal? regulatory? zoning, given siblings) is never named.

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 indication of when to call this versus any sibling such as get_zoning, check_use_allowed, or get_site_report. No prerequisites, exclusions, or alternatives are mentioned anywhere in the text.

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