netsuite_get_employees

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

With no annotations, the description carries full behavioral burden. It correctly identifies a read operation ('List') but does not disclose default pagination behavior, search field semantics, or return format. It adds minimal behavioral context beyond the obvious.

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?

Three short sentences: purpose, use case, parameter list. Front-loaded and every sentence is informative; no waste.

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?

The tool has no annotations and no output schema, so the description must cover purpose, usage, and params. It does well on all three, but omits return value structure and default pagination behavior. Adequate for a simple list tool but not fully complete.

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?

The description explicitly lists all three parameters with types and brief semantics: q is a 'search query', limit and offset are for pagination. This adds meaning beyond the schema's bare type definitions, though it could detail which fields q searches.

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 opens with 'List NetSuite employees' (specific verb+resource), mentions optional search/pagination, and states its use case (matching Spendesk Members to NetSuite Employees). This clearly distinguishes it from siblings like netsuite_get_employee, which likely fetches a single employee.

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?

It provides a concrete scenario ('Used to match Spendesk Members to NetSuite Employees for expense reports'), giving clear context. However, it doesn't explicitly mention alternatives or when not to use it, such as when a single employee is needed via netsuite_get_employee.

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