Upload Video

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

Annotations (all false) are consistent with a write operation. Description adds return object details and safety default. Could mention async processing or file size limits but overall good transparency.

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?

Well-structured with a clear header and bullet-pointed args. The Args list is thorough but not overly verbose. Could trim redundant phrasing but still concise.

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?

Covers upload process, parameter combinations, and return values. Lacks file size limits or authentication prerequisites. Given the complexity and many siblings, it sufficiently distinguishes from other tools.

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?

Despite empty input schema, description compensates fully with a detailed Args list covering data types, defaults, required/optional, and enum mappings (privacy, age_restriction). Schema coverage is effectively 100% due to documentation.

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 'Upload a video to Neptime.io' with a specific endpoint, distinct from sibling tools like update_video or delete_video. It specifies the resource and action unambiguously.

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?

Provides explicit guidance on choosing between video_path and video_base64, listing required args and defaults. Lacks explicit 'when not to use' but given it's the only upload tool, the guidance is adequate.

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