list_prompts

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states 'Fetch prompts' and returns 'Dict with prompts and metadata.' It does not disclose pagination behavior, ordering, auth requirements, or any side effects. For a read operation, this minimal detail is a significant gap.

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 followed by Args and Returns sections. It is concise and front-loaded, though the Args section duplicates schema info, which is slightly redundant. Still, it avoids waste and maintains a clear structure.

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 a low-complexity schema but no output schema. The description only gives a vague return type ('Dict with prompts and metadata') without explaining the structure, pagination, or filtering semantics. Given the lack of annotations and output schema, more contextual detail is needed for correct invocation.

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 schema provides 100% coverage of both parameters with descriptions and defaults. The description's Args section simply reiterates the schema information without adding new meaning, so it does not compensate beyond the existing schema coverage.

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 'Fetch prompts from LangSmith with optional filtering' which clearly identifies the operation (fetch/list) and resource (prompts). It distinguishes from siblings like get_prompt_by_name (which fetches a single prompt) by implying a list operation with optional filters.

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 provides no guidance on when to use this tool versus alternatives such as get_prompt_by_name or other list tools. It mentions optional filtering but does not state exclusions or alternative references, leaving the agent without decision-making context.

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