save_artifact

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

With no annotations provided, the description carries the behavioral transparency burden. It usefully discloses that artifacts are stored as files with metadata indexed in SQLite and that shared=True saves to a shared directory. However, it does not mention overwrite behavior, return value, idempotency, or potential failure modes, which would be valuable for a write tool.

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 well-structured with clear sections for triggers, workflow position, and parameters, making it easy to scan. There is minor redundancy between 'AUTOMATIC TRIGGERS' and 'WORKFLOW POSITION', but overall each section earns its place.

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 provides enough context for an agent to decide when to use the tool and how to fill parameters. It lacks output schema information and does not clarify the relationship with save_finding, but for a save operation the provided details are largely sufficient.

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, and it does. All seven parameters are listed with concise but meaningful explanations, including artifact_type examples and the effect of shared=True. This adds value beyond the raw 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 saves a research artifact (finding, analysis, summary) to the session, with specific examples and automatic trigger conditions. It is unambiguous about the action and resource, though it does not explicitly distinguish itself from the sibling save_finding tool.

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 provides explicit trigger conditions for when to call the tool, including completing significant analysis, writing important code/documentation, and saving detailed analyses. It also gives a clear exclusion ('not for inline messages'), though it does not mention alternative tools like save_finding for comparison.

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