enrich_employee_list

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

The annotations already declare readOnlyHint and openWorldHint, covering safety and data completeness. The description adds valuable behavioral context: cost (3 credits per employee returned) and the type of data returned (profile URLs and basic info). However, it does not mention pagination, caching, or other runtime behaviors beyond what is in param descriptions, but the added cost detail is notable.

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 extremely concise: two short sentences that state the action, return type, and cost. No wasted words, front-loaded with the primary purpose. It communicates everything necessary in minimal length.

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?

Despite having 10 parameters and no output schema, the description is very brief. It does not explain the output format (e.g., pagination, fields), or offer usage examples. While param descriptions cover individual parameters, the overall operational context is thin. The read-only and open-world annotations help, but for a tool with this many options, more context would improve completeness.

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 all 10 parameters are documented with descriptions and enums. The tool description itself adds no parameter-specific meaning beyond the high-level purpose. Baseline for high coverage is 3, and the description does not enhance or clarify any parameter semantics further.

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 lists employees of a company and returns profile URLs and basic info. It uses a specific verb ('List') and resource ('employees of a company'), and distinguishes from sibling tools like enrich_employee_search (search) and enrich_employee_count (count) by its focus on listing all employees.

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 any guidance on when to use this tool versus alternatives. It lacks mention of use cases, prerequisites (like needing a company URL), or exclusions. No comparison with sibling tools like enrich_employee_search is offered, so an agent may not know if this is the best choice for a given scenario.

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