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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only adds that it is browser-based, which is a superficial trait. It does not mention what happens to the video, whether it is processed locally or uploaded, any file size limits, or the expected output format. This lack of detail leaves the agent with significant uncertainty about the tool's behavior.

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 extremely concise, consisting of two short sentences that immediately state the purpose and environment. There is no redundant information or filler. Every word contributes to a clear, front-loaded message.

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?

Given the low complexity (no parameters) and lack of output schema, the description is still insufficiently complete. It fails to explain what 'optimize' entails, what the user can expect, or any constraints. For a tool with many sibling video tools, the description provides only minimal differentiation and lacks essential context to guide the agent in invoking it correctly.

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 input schema has zero parameters, so the baseline of 4 applies. The description adds the 'browser-based' context, which is not relevant to parameter semantics but is the only additional detail. Since there are no parameters to explain, the description does not need to compensate, and it fully covers the schema's emptiness.

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 that the tool optimizes videos for Instagram Reels and Stories, using a specific verb and target platform. This distinguishes it from sibling tools like video-duration-calculator and the YouTube-focused yt-* tools. However, the verb 'optimize' is somewhat broad and could encompass various operations (resize, crop, enhance), leaving some ambiguity about the exact function.

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 usage for preparing videos for Instagram Reels and Stories by explicitly naming the platform. However, it provides no explicit guidance on when to choose this tool over alternatives, nor does it mention any exclusions or specific scenarios. The platform specification is an implicit cue, but there is no direct comparison or conditional advice.

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