Fetch a list of published pick-up line collections, including URL, title, BCP-47 language, and line count. Use it to browse available multilingual content.
List published pick-up line collections: URL, title, language (BCP-47) and line count.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It transparently states the operation is a list, the 'published' filter, and the exact output fields. It does not discuss pagination or response shape, but for a simple no-parameter read tool this is reasonably complete.
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?
One sentence with no filler: it states the action, the resource, and the output fields. Every element earns its place and the key information is front-loaded.
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 zero-parameter, no-output-schema tool, the description names the output fields and the 'published' scope. It does not specify the response container or pagination, but nothing critical is missing for selecting and invoking this 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 tool has zero parameters, so the baseline is 4. The description adds useful output-field semantics (URL, title, language, line count) even though no parameter documentation is needed.
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 uses a specific verb ('List'), a clear resource ('published pick-up line collections'), and enumerates the returned fields (URL, title, language, line count). This clearly distinguishes it from sibling tools that operate on individual lines or search them.
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 clearly establishes the tool's purpose: to list published collections. It does not explicitly name alternatives or exclusions, but the context is clear enough that no prerequisites or competing conditions are needed for this no-argument list operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.