list_examples

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

No annotations are provided, so the description carries the burden. It states that one of three parameters must be provided, which is a behavioral constraint, but it does not disclose read-only status, auth requirements, or pagination behavior. The word 'Fetch' implies read-only, though not explicitly.

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 structured with a summary line, a requirement line, and a parameter list. It is clear and front-loaded, but somewhat redundant with the schema as every parameter description is duplicated, adding length without much new information.

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?

With 11 parameters and no output schema, the description covers all inputs but does not explain the return format, pagination, or error behavior. The 'advanced filtering options' are merely listed without further explanation, leaving some gaps for a complex tool.

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 repeats the parameter list, which matches the schema's 100% coverage. It adds the requirement that one of dataset_id, dataset_name, or example_ids must be provided, which is useful beyond the schema. No additional syntax or format details are given beyond the schema descriptions.

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 'Fetch examples from a LangSmith dataset with advanced filtering options' with a specific verb and resource. It also clarifies that one of dataset_id, dataset_name, or example_ids must be provided. This distinguishes it from sibling tools like list_datasets or read_example by focusing on examples and filtering.

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 usage for retrieving multiple examples with filtering and requires at least one identifier, but it does not explicitly compare itself to alternatives like read_example for single-example retrieval or mention when not to use it. It provides context but no clear exclusions or alternatives.

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