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

No annotations are provided, and the description fails to disclose behavioral traits such as whether the operation is read-only, any authentication requirements, or return value characteristics. The description focuses solely on parameter semantics, leaving the agent unaware of side effects or constraints.

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 reasonably concise but could be better structured. The parameter details are presented as a bullet list without clear indication of required vs optional. It is not overly verbose, but the lack of a summary or example makes it less efficient.

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?

The description does not explain the return format, which is important given no output schema. It also fails to mention that all parameters are optional or how the search behaves with no parameters. Additional context like result ordering, pagination, or error cases is missing.

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?

The description adds significant meaning beyond the input schema, which only provides types and defaults. It explains sub_vertical values ('environmental_compliance' | 'accessibility' or free-text), region matching (case-insensitive contains), capability keyword matching, and limit max results. This compensates for the 0% schema coverage.

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's purpose: 'Search the Compliance Registry for vetted compliance and regulatory firms.' It uses a specific verb (Search) and resource (Compliance Registry), and distinguishes this search tool from sibling tools like get_firm_profile or claim_listing.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. The usage context is implied by the parameter descriptions, but no exclusions or prerequisites are stated.

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