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

No annotations provided, so description carries full burden. Describes data source (U.S. DOL), aggregation, and output fields. Does not explicitly state read-only or rate limits, but search behavior is clear and safe.

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?

Description is structured with purpose first, then details. Four sentences, no redundancy. Slightly verbose but efficiently conveys necessary information.

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?

Given 3 optional params and no annotations, description covers filters, output fields, ranking, and data source. Lacks pagination details and error handling, but is largely complete for a search tool. Output schema exists, so return values are additionally documented.

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%, but description explains query (employer name) and state (2-letter code). Limit parameter is not described but has a default. Adds value by clarifying parameter meaning beyond schema.

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 US employers that sponsor H-1B visas, specifies filters (query and state), mentions ranking, and lists output fields. It distinguishes from sibling tools like get_h1b_sponsor_details and other category-specific search tools.

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?

Describes when to use (searching H-1B sponsors for Indians-from-India) and provides filter context. Lacks explicit when-not-to-use or alternatives, but sibling tools cover other categories, so usage boundaries are implied.

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