easysourceflow_summarize_link

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

Annotations are present and consistent. The description adds behavioral details: synchronous execution, final Markdown output, and the instruction to relay verbatim. No contradictions.

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 a single paragraph covering purpose, exclusions, output handling, and delivery. It is relatively concise but could be broken into separate points for clarity.

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?

Despite lacking an output schema, the description fully explains the output (Markdown) and how to handle it. It also covers key constraints and usage context, making it complete for an agent.

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 covers all parameters with descriptions. The description adds context about the URL type (short non-video webpage) beyond the schema, but parameter details are already solid.

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 the tool summarizes a short non-video webpage. It distinguishes from video content and specifies that it returns final Markdown for direct user delivery.

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?

Explicitly advises against using for Bilibili or YouTube, and provides the alternative workflow (easysourceflow_submit_link + get_job). Also gives detailed instructions on how to deliver the result (verbatim in message card).

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