enrich_employee_count

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

Annotations include readOnlyHint=true and openWorldHint=true, which already inform the agent that this is a safe read operation and may return variable results. The description adds the cost (1 credit) which is a behavioral trait not covered by annotations. However, it does not disclose other behaviors like whether the count is estimated or exact, or how the 'use_cache' parameter affects freshness. Given the annotations cover the safety profile, the description adds some value but not extensive behavioral context.

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 concise: one sentence plus a cost note. It is front-loaded with the main purpose. The cost information is useful and earns its place. No fluff or redundancy. However, it could be slightly more structured by including usage guidance, but for what it is, it's 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?

Given the tool has 6 parameters, 4 with enums, and no output schema, the description is somewhat thin. It does not explain the return format (e.g., just a number or an object), nor does it clarify the meaning of parameters like 'coy_name_match' or 'employment_status' beyond their schema descriptions. The annotations help with safety, but the description could be more complete for a tool with this many options. However, since schema coverage is 100%, the description doesn't need to repeat parameter details, but it could provide more context on how the tool behaves (e.g., what 'estimated_employee_count' means).

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 6 parameters have descriptions in the schema. The description itself does not add any parameter semantics beyond what the schema provides. According to the rubric, with high schema coverage, baseline is 3. The description does not compensate with additional context, so a 3 is appropriate.

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: 'Get the number of employees at a company.' It uses a specific verb ('Get') and resource ('number of employees at a company'), which distinguishes it from sibling tools like enrich_employee_list (which likely returns a list) and enrich_company_profile (which likely returns broader company data). However, it doesn't explicitly differentiate from similar count tools like enrich_job_count, but the resource is clear enough.

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 provides minimal usage guidance. It mentions the cost (1 credit) which is a practical consideration, but does not specify when to use this tool versus alternatives like enrich_employee_list or enrich_company_profile. The context signals show many sibling tools, but the description doesn't offer any comparison or exclusion criteria. The 'at_date' parameter implies historical usage, but this is not explained in the description.

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