Run any Poe media bot

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the side-effect profile at a high level ('optional local file attachments' sent, 'download whatever media it returns'), implying files are written locally. However it says nothing about authentication, rate limits, failure behavior for unknown bot names, or where/whether files are returned — significant gaps for a tool that performs network calls and disk writes.

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?

Two sentences, zero filler, with the core action front-loaded and the routing guidance immediately after. Every clause earns its place.

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 6-parameter tool with no output schema and no annotations, the description covers purpose, routing, and the general input/output shape (prompt + attachments in, media files out). It is largely complete, but given the absence of annotations it could say more about return values, file destinations, and failure modes.

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 description coverage is 83%, so the schema already documents model, output_dir, parameters, attachments, and prompt_flags in detail (including the poe.com/<bot>/api pointer). The description adds only a loose reference to 'optional local file attachments', which maps to the already-documented attachments param. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Call any Poe bot by name... then download whatever media it returns') and immediately carves out its niche relative to siblings by saying it is for bots 'the dedicated tools don't cover' and listing examples (upscalers, lip-sync, sound effects, background removal). An agent can distinguish this from generate_image/generate_video/generate_speech/generate_music without opening a schema.

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?

Gives explicit when-to-use and when-not-to-use guidance: use it for bot categories the dedicated tools do not cover, with concrete examples. The alternative (the dedicated sibling tools) is referenced as the comparison set, which is enough to route correctly.

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