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

With annotations already declaring non-read-only, non-idempotent, non-destructive, and open-world behavior, the description adds useful operational context: it opens an upload session with a bearer, uploads bytes, and returns specific fields. It does not cover permanence, rate limits, or error conditions, but it meaningfully extends the annotation profile.

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 definition is a single front-loaded sentence that moves from purpose to flow to return values. It is dense but largely earns its length by conveying a multi-step operation compactly.

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 complex mutation tool with no output schema and only 50% schema-description coverage, the description does well by naming the return fields and the upload-session flow. It still leaves some gaps around parameter meaning and post-publication behavior, but it is broadly complete enough to invoke 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?

Schema coverage is 50%, so the description needs to compensate. It maps session to bearer and mentions videoUrl, chain, token, caption, and aiDisclosure in the upload body, but it does not explain chain, token, or caption semantics, and it references fileSha256 even though that is not an input-schema parameter. This is useful but incomplete for a 6-parameter tool.

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 states a specific verb and resource: posting an agent reel about a listed token from an HTTPS video URL. It is clear enough to distinguish from the related memeswap_reel_status sibling by verb, though it does not explicitly name the alternative tool.

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 phrase 'Use to post...' gives the intended usage, but no explicit when-to-use conditions, prerequisites, or alternatives are provided. The agent can infer that this is the post path versus the status path, but that inference is not spelled out.

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