Get a sample of the newest public adult videos on DesAira (max 20).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) | |
| cursor | No | Opaque pagination cursor from a prior call | |
| per_page | No | Items per page (max 20) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| videos | No | ||
| has_more | No | ||
| next_cursor | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the disclosure burden. It discloses that the feed is a sample, is limited to newest public adult videos, and caps at 20 items, but it does not explain pagination behavior, stability of ordering, or whether any authentication is required.
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?
A single sentence conveys the action, resource, scope, and limit without any filler. The key constraint is front-loaded, making it easy for an agent to parse quickly.
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 simple feed-reader with full schema coverage and an output schema, the description is mostly sufficient. It lacks explicit usage guidance and deeper behavioral notes, but it covers the essential purpose, scope, and size limit.
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 schema already documents page, cursor, and per_page. The description adds only the 'max 20' context already present in the schema, providing no additional parameter-level meaning.
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 and resource: 'Get a sample of the newest public adult videos on DesAira.' It clearly distinguishes the tool from siblings like get_trending, get_user, and search_content by scoping it to newest public videos with a max of 20.
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 the tool is for accessing a latest-videos feed, but it does not explicitly say when to use it instead of get_trending or search_content. No exclusions or alternative routing guidance is provided, leaving usage context mostly implicit.
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.
