list_sales_employees

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

No annotations are provided, so the description carries the full burden. It mentions the data source (gate_sso dblink) and capabilities (pagination, search, sorting), but does not explicitly state whether the operation is read-only or if it has side effects. For a list operation, this is acceptable but lacks full transparency.

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 a single sentence that immediately states the purpose and key capabilities (pagination, search, sorting). It is front-loaded and contains no superfluous information. Every word contributes value.

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 5 parameters with full schema coverage but no output schema. The description adds the data source context. For a list tool, this is adequate but could mention expected output fields or additional details about search behavior. It is not incomplete, but not richly 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 input schema covers 100% of parameters with descriptions, so the schema already provides meaning. The description does not add any additional explanation beyond what the schema contains. Baseline score of 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 retrieves a list of sales employees from a specific source (gate_sso dblink) with pagination, search, and sorting. It uses a specific verb ('Ambil daftar') and resource ('sales employee'), and distinguishes itself from sibling list/get tools by mentioning these features.

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 implies the tool is for listing sales employees with pagination/search/sorting, but provides no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. The usage context is inferred but not explicitly stated.

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