save_report

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

No annotations are provided, so the description carries the burden. It discloses the save location ('reports/' folder next to the CSV), default directory behavior, and how include_plots works (saves named plots as PNG, reference syntax provided). It does not mention overwrite behavior or failure modes, but it adds significant context beyond the schema.

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 bit long but every sentence adds value: purpose, usage context, file locations, defaults, plot handling, and an example. It could be slightly more compact, but it is well-structured and not redundant.

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?

The description covers the main behavior, defaults, and plotting integration, with an example. However, it omits details like how the markdown file is named, whether existing files are overwritten, and it does not contrast with the sibling save_report_html. These gaps prevent a 5, but the example and default explanation make it fairly complete.

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 coverage is 0%, so the description must compensate. It explains output_dir's default and fallback, include_plots' behavior as saving named plots as PNG, and the example clarifies content as a markdown string. This fully conveys how to use all three parameters.

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 saves a data science report as a markdown file with associated plot images. It specifies the resource (report), format (markdown), and differentiates from siblings like save_report_html by mentioning markdown explicitly.

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?

It explicitly says to use this as the FINAL STEP of an analysis to export a structured, presentable report. This provides clear context, but it does not mention when not to use it or alternative tools (e.g., save_report_html), so it lacks exclusions and alternatives.

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