search_license

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the scope and use case but does not describe any behavioral traits such as whether it requires either name or license number, returns results from multiple states, or has any side effects. This is a significant gap for a search 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?

The description is two sentences with no extraneous information; it is front-loaded with the action and resource, and the use-case sentence earns its place. Perfectly concise.

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 simple search tool with full schema coverage, the description provides the core purpose and a usage hint. However, it lacks any mention of return value, input requirements, or result behavior, and with no annotations, it doesn't fully cover the context. It is minimally adequate but has gaps.

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 100%, so the baseline is 3. The description adds context that the states parameter can be omitted when the state is unknown, reinforcing the default to all states. This adds meaningful behavior beyond the schema descriptions, warranting a 4.

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 searches for a professional license across multiple states, with a specific verb and resource. It also distinguishes itself from siblings by emphasizing the multi-state scope and the use case of unknown state, differentiating from verify_license.

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 clear context for when to use this tool ('when you don't know which state issued the license'), indicating the appropriate scenario. However, it does not explicitly mention alternatives or exclusion criteria, such as using verify_license when the state is known.

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