download_news_attachment

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

With no annotations, the description must convey behavioral traits. It states 'using the authenticated session' implying authentication is required, but fails to disclose side effects like file creation, overwrite behavior, or what happens on error. The download action and file system side effects are insufficiently described.

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 very concise with one short sentence, but it omits crucial details. While it has no wasted words, it is under-informative for the complexity of the tool. A slightly longer description would be more helpful.

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?

Given the 3 parameters and no output schema, the description is incomplete. It does not explain the return value (e.g., saved file path or success message), error handling, or common use cases. The schema covers parameters, but the tool's overall behavior and results are under-described.

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?

The input schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate. The parameters (newsId, index, outputDir) are clear from the schema.

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 uses a clear verb 'download' and specifies the resource 'news article attachment'. It is distinct from sibling tools like 'get_news' and 'get_news_detail' which are read-only. However, it lacks detail about which attachment (index) and the fact that it saves to a directory.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., needing the newsId from another tool) or context about the authenticated session. The description is too minimal to assist an agent in deciding tool usage.

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