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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context by noting pagination and enumerating the returned fields (name, title, headline, email, LinkedIn URL). It also clarifies that employees are shared leads tied to a company, which is non-obvious from the tool name.

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?

Two sentences with no filler. The first sentence states the action and scope, and the second adds return-field detail and a pointer to the population tool. Every clause earns its place.

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?

For a paginated list endpoint with read-only annotations and no output schema, the description covers the main retrieval contract: what is listed, how it is paginated, what fields are returned, and how to refresh the underlying data. It could have mentioned cursor semantics or ordering, but for this tool's complexity the coverage is strong.

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%, so the description should compensate by explaining companyId, limit, and cursor. It only implies companyId via 'for a company' and pagination via 'paginated', but does not explain cursor continuation, default limit, or how parameters map to the listing behavior. The schema names are self-explanatory, but the description adds little parameter-level value.

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 states a specific verb ('List'), resource ('employees stored for a company'), and scope ('shared leads tied to it'), making the tool's purpose immediately clear. It also differentiates the tool from nearby siblings such as campaignstack_list_company_employee_watches by emphasizing stored employee records rather than watches.

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 tells the agent that this reads stored employees and explicitly points to campaignstack_extract_company_employees for populating or refreshing the set. It does not exhaustively list when not to use it, but the naming of the related extraction tool gives practical routing guidance.

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