save_artifact

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

Annotations already indicate this is a non-read-only, non-destructive, idempotent operation. The description adds the 'allow-listed' constraint and 'case folder' destination, but does not disclose overwrite behavior, validation rules, or what happens when the artifact is not allow-listed. It is consistent with annotations and adds modest context.

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 single, front-loaded sentence with no redundant wording. Every word contributes meaning, and the core action and target are immediately clear.

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, no parameter descriptions, and only minimal annotation coverage, the description is too sparse for an agent to call this tool correctly in all cases. It does not explain what 'allow-listed' means, what content should contain, filename constraints, or the expected result of the save operation.

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 0%, so the description must compensate for the three undocumented parameters. It clarifies the general purpose of case_folder but does not explain the expected format or semantics of content or filename, leaving the agent to infer from property names alone.

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 states a specific verb ('Save'), a specific resource ('allow-listed pipeline artifact'), and a target location ('case folder'). This clearly differentiates it from siblings like save_draft_as_docx and read_case_folder without needing to inspect the 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?

The phrase 'allow-listed pipeline artifact' implies a precondition for use, but the description does not explicitly state when to use this tool versus alternatives such as save_draft_as_docx or create_case_folder. Usage context is implied rather than stated.

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