save_material

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

With no annotations provided, the description bears full responsibility for disclosing side effects. It explicitly states that the tool downloads, never overwrites, reports identical content as 'duplicate', and stores changed content under a dated name—covering key behavioral traits.

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 two sentences long, directly states the primary action, and explains the duplicate/versioning behavior. It is well-structured and free of unnecessary details, making it easy to parse.

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 that an output schema exists, the description does not need to explain return values. It provides sufficient context about the save behavior, duplicate handling, and file naming, though it does not mention prerequisites or error conditions beyond duplicates. Overall, it is complete enough for the tool's purpose.

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% for all three parameters, so the baseline is 3. The description adds minimal extra meaning beyond the parameter descriptions—it confirms the url is the document source and fund_id refers to the fund, but these are already in 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 clearly states the tool downloads a document into the fund's Materials directory, specifying the action and resource. It also mentions duplicate handling, which distinguishes it from listing or syncing tools. The verb 'Download' is specific and unambiguous.

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?

The description explains how the tool behaves (never overwrites, reports duplicates, uses dated names) but does not explicitly state when to use this tool versus alternatives like list_materials or sync_db. The usage is implicit rather than directly contrasted with sibling tools.

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