lob_list_templatesList saved HTML templates usable as postcard/letter artwork. Lob API: GET /v1/templates.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor for the next page (from a previous response's next_url). | |
| limit | No | Max results per page (1–100). Default 10. | |
| before | No | Cursor for the previous page (from a previous response's previous_url). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already signals safe read behavior. The description adds context about the content (HTML templates for postcards/letters) and the API endpoint, but does not detail pagination or rate limits. With annotations covering the safety profile, the additional value is moderate.
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, no wasted words. Front-loaded with the core purpose and followed by the API endpoint. Extremely efficient.
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?
No output schema is provided, and the description does not explain the shape of the returned data (e.g., an array of template objects). However, the tool is simple and the purpose is clear; the missing output information is a gap but not critical for basic usage.
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 coverage is 100%, so the baseline is 3. The description does not add any parameter-specific details beyond the schema's own descriptions of 'after', 'limit', and 'before'.
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 verb 'List' and the resource 'saved HTML templates', specifying their use as postcard/letter artwork. It also references the API endpoint, distinguishing it from sibling list tools (e.g., lob_list_addresses, lob_list_letters) which list different resource types.
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 clear context for when to use the tool (to list saved templates for artwork), but does not explicitly exclude alternatives or provide when-not-to-use guidance. Given the simplicity of the operation, this is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource and action, with clear verb-noun names like create_address and verify_us_address. There is no overlapping functionality, and even similar operations (e.g., list for different resources) are distinct.
All tools share the 'lob_' prefix and follow a consistent verb_noun pattern (e.g., create_postcard, list_letters, verify_intl_address). Multi-word nouns use underscores, maintaining uniformity throughout.
With 18 tools, the set covers the primary mail fulfillment operations—address management, postcards, letters, checks, self-mailers, and address verification—without feeling bloated or sparse. The count is well-suited to the domain.
The tool set has notable gaps: no create_check or create_self_mailer, no cancel for letters or checks despite being referenced, no update/delete for addresses, and only list for templates. These missing operations will likely cause agent failures in common workflows.