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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, and the description reinforces the non-idempotent, creates-a-new-job semantics ('Start a NEW ... job', 'creates a job and begins processing'). It also discloses the return contract (job ID / mediaId) despite the absence of an output schema, though it says nothing about quotas, auth requirements, or failure modes for inaccessible URLs.

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?

Three sentences, each earning its place: the core action and inputs first, the disambiguating exclusion second, and the return value last. No filler or repetition.

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?

With no output schema, the description supplies the missing return contract (job ID used to track processing), and it names the follow-up tools conceptually. Combined with full parameter coverage and annotations, an agent has everything needed to call 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?

Schema description coverage is 100%, so both url and mediaType are already documented, including the accepted URL forms and the enum values. The description's media-type list largely restates the enum rather than adding syntax or constraints beyond the schema, so the baseline 3 applies.

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 ('Start a NEW Echosaw analysis job from a ... URL') and explicitly names the sibling it is not ('it does not fetch previously analyzed media — use echosaw_download_media'). An agent can distinguish it from echosaw_download_media and echosaw_get_analysis_results without opening any 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 the use condition (start processing from a public or platform URL) and an explicit exclusion with the alternative tool for the confusable case (retrieving already-analyzed media). It also enumerates acceptable input categories, so the agent knows when this tool applies.

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