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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that: default page size (25), a hard cap (200), the field-naming convention of the Laudus data model, and the underlying POST /sales/salesmen/list endpoint. It does not say whether a total count or cursor is returned.

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 sentences, front-loaded with purpose, then the paging rule, then the field-naming and endpoint details. The page-size figures lightly duplicate the schema but are cheap and reinforce the paging logic.

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?

There is no output schema, so the description carries the burden of explaining the response, and it never says what a result row looks like or whether a total/has-more indicator is returned — the reader must infer that from the paging instruction. For a read-only list tool with fully documented parameters this is adequate but leaves a real gap.

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 the baseline is 3. The description earns above baseline by adding the field-naming model with concrete examples (salesmanId, name), which tells the agent what strings are legal in `fields`, `filter` and `order_by` — context the schema itself leaves abstract.

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?

States a specific verb+resource ("List salespeople (vendedores)") and enumerates the capabilities: filters, sorting, field selection and paging. No sibling lists salespeople, so the resource alone disambiguates it from laudus_list_customers, laudus_list_suppliers and the other list_* tools.

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?

Gives concrete operating guidance for paging: "When a page is full, ask for the next one with offset = offset + limit." That is actionable when-to-use advice. It stops short of explicit exclusions or pointing to an alternative tool, but there is no competing tool for this resource.

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