webex_save_file

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

No annotations exist, so the description carries the entire behavioral burden; it does disclose the 100 MB ceiling, the exact destination directory template, the overwrite-on-existence behavior, and a security warning. It omits what happens when the file exceeds 100 MB (error vs truncation), whether authorization comes from the URL or from the caller's credentials, and how partial or failed writes are handled.

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 dense, semicolon-delimited single paragraph front-loads what the tool does, then size, then destination, then risk. Every clause carries information, though the telegraphic phrasing is slightly harder to parse than plain sentences.

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 one-parameter local-write tool with no output schema, the description covers the practical essentials: destination path resolution, overwrite semantics, size limit, and the returned path. The main remaining gap is failure behavior at the size boundary and where the download credentials come from.

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?

With a single parameter at 100% schema coverage the schema already explains fileUrl as the "Message files[] contents URL", and the description adds nothing about URL form, expiry, or authentication. The path template incidentally clarifies that a message uuid is derivable from the URL, which is mild added meaning.

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?

"Save attachment to local disk" states a concrete verb and resource, and the size cap and returned path sharpen it. It does not distinguish itself from its close siblings webex_download_file and webex_save_message_files, so an agent must infer the boundary rather than read it.

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?

"returns path for local readers" implicitly signals when to prefer this over a streaming download, and "never execute untrusted downloads" is a safety caveat rather than a usage rule. There is no explicit when-to-use guidance and no named alternative among the sibling file tools.

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