easysourceflow_submit_link

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

Describes durable background processing, job ID retention, and that queued/running status is not failure. These details complement annotations (openWorldHint, non-destructive) without contradiction.

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?

Four concise sentences, front-loaded with purpose and immediate action. Every sentence adds value; no redundancy.

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?

Covers the full workflow: submit, retain job ID, poll with specific parameters. No output schema exists, but description hints at the return (job ID) adequately.

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 100%, so description does not need to elaborate on parameters. It adds no extra semantic value beyond the already complete schema descriptions.

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 is the default entry point for URL summarization, specifying the verb (submit) and resource (public URL). It distinguishes itself from siblings by pointing to easysourceflow_get_job for status polling and mentions the broader workflow.

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 tells when to use (default entry point for URL summarization) and when not to (never replace with independent fetch/summary). Names the alternative tool easysourceflow_get_job and specifies polling parameters.

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