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

With no annotations, the description must carry behavioral context. It usefully discloses that processing happens in the browser, consumes more credits per run, and is excluded from Day Pass coverage. However, it does not explain how input video is supplied, whether operations are reversible, or what the saved output location is.

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 purpose sentence is front-loaded and useful, but more than half the description is repeated credit and pricing information that belongs in mioffice_pricing_info. There is also a duplicated 'for TikTok' phrasing and a stray double period, reducing polish.

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 tool with no output schema, the core output specification is present. The description still leaves unclear how a source video is provided or launched, which is significant given the absence of input parameters and any output schema.

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 has zero parameters, so there is no parameter semantics burden. The description correctly implies a fixed, preset TikTok export without configurable inputs, matching the empty 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 gives a specific verb and output: create a 1080 × 1920 vertical MP4 for TikTok. That clearly distinguishes it from generic resize tools by target platform and aspect ratio. It does not explicitly name sibling alternatives like mio_video_resize_reels or mio_video_resize_shorts, so it falls short of full sibling differentiation.

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?

It offers workflow hints such as reviewing the centered crop and keeping default export settings, but never states when to choose this over mio_video_resize, mio_video_resize_reels, or mio_video_resize_shorts. The remaining text is pricing boilerplate, not usage guidance.

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