Get a sample of the newest public DesAira videos (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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It notes that videos are public and limited to a sample of 20, indicating a read-only, low-sensitivity operation. However, it does not explicitly state the absence of side effects, authentication needs, or rate limits, though 'public' and 'get' imply a safe read.
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 concise sentence that front-loads the action and resource. Every word earns its place, with no waste or repetition.
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 an output schema and simple optional pagination parameters. The description provides the essential purpose and limit, though it could clarify that pagination is available via the provided cursor/page parameters. Overall, combined with the schema, it is sufficiently complete for a basic feed retrieval.
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 fully describes all three parameters (page, cursor, per_page) with 100% coverage. The description only redundantly mentions 'max 20' (already in per_page's schema) and adds no additional meaning to the parameters, so the description provides no extra value beyond the schema.
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 identifies the tool as retrieving the newest public DesAira videos, with a size limit of 20. The verb 'get' and resource 'videos' are specific, and 'newest' distinguishes it from get_trending (trending) and get_video (single item), making the purpose unambiguous.
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 a use case of browsing recent public content but does not explicitly mention alternatives or when to use this tool versus siblings like get_trending or get_video. No exclusions or prerequisites are stated, so guidance remains only implied.
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.
Each tool targets a distinct resource and retrieval mode: feed and trending differ by sorting, user and video are specific entities, creators and tags are directory listings, and search is a cross-cutting keyword query. No two tools are ambiguous in purpose.
All tool names follow a consistent snake_case verb_noun pattern, using get_ for entity retrieval, list_ for directory browsing, and search_ for keyword search. The naming is predictable and uniform.
Seven tools is an ideal size for a video platform's public API, covering browsing, discovery, and search without redundancy or bloat. Each tool earns its place in the set.
The server provides a comprehensive read-only surface: chronological feed, trending, user profiles with recent videos, video metadata, creator directory, tag categories, and keyword search. This fully covers the stated purpose of public content exploration with no obvious gaps.
