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

No annotations are provided, so the description carries the full behavioral burden and falls short. It never states whether this is read-only, whether results are paginated or rate-limited, what a match returns, or how partial name matches behave — all material for an agent invoking a search.

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?

Front-loaded one-line purpose followed by a compact Args list; nothing is padded. The Args block partly repeats schema titles but earns its place through the license_type enum and state format.

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 output schema and no annotations, the description should do more than enumerate inputs — it says nothing about result shape, coverage limits per source, or match semantics. Adequate for calling the tool correctly, incomplete for interpreting results.

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%, so the description has to compensate, and it mostly does: it defines entity_name as licensee name, gives the accepted license_type values ('npi' | 'medical' | 'fcc' | 'radio' | 'all') that appear nowhere in the schema, and specifies state as a 2-letter code. It omits defaults/nullability behavior.

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?

States a specific verb and resource — searching professional/business licenses — and hints at scope with the source list (NPI + FCC). It doesn't differentiate itself from the sibling mcp_lookup_npi, so an agent has no guidance on which license tool to pick.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives despite a crowded sibling set including mcp_lookup_npi and mcp_verify_entity. The parenthetical 'more sources roadmap' is informational, not routing guidance.

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