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

No annotations are provided, so the description carries the full burden of behavioral disclosure and largely drops it. It never says whether results are paginated or capped, whether the search is exact-match or fuzzy, whether it requires authentication/licensing scope, or whether omitting all filters returns the whole directory — all material for a six-parameter discovery tool.

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?

A single tight sentence with the resource and the filter axes front-loaded. Nothing is redundant and nothing needs trimming.

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 no annotations, no output schema, and six undocumented parameters, the one-line description is insufficient for an agent to call this correctly. At minimum it should explain the query parameter, the default role behavior, and whether unfiltered calls return the full directory.

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 0% and the description only gestures at four of the six parameters in generic prose ('location, role, specialty, or certification'), collapsing city and state into 'location'. The free-text 'query' parameter is left entirely unexplained in both schema and description, and there is no guidance on formats or on the appraiser/umpire/both role enum.

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 and resource — searching a directory of certified insurance appraisers and umpires — and names the filter dimensions. It distinguishes itself implicitly from get_appraiser_profile (lookup of one known entity) by framing this as directory search, though it never names the siblings outright.

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?

Usage is only implied: the agent can infer 'use this to discover appraisers by attribute' from the listed filters. There is no explicit when-not guidance, no note on what an empty search returns (all records vs. an error), and no reference to get_appraiser_profile or explain_appraisal_process as alternatives.

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