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

The description discloses meaningful behavioral context beyond the annotations: the write-tier approval flow, the difference between from-now-on and just-once approval, and the 'card is the yes' guidance. Annotations already signal mutation via readOnlyHint=false and destructiveHint=true, so the description does not need to repeat those. It adds legitimate orchestration value.

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 core purpose and usage are front-loaded in the first two sentences. The second paragraph about approvals is a bit dense but is genuinely useful operational guidance, not filler. It earns a 4 because every part contributes value, though it could be slightly tightened.

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 seven parameters and no output schema, the description covers the main usage triggers and the approval nuance, while the schema handles parameter meaning. It does not describe the return value or what a successful save looks like, but the guidance is otherwise sufficient for an agent to invoke it correctly in context.

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%, so the input schema fully documents all seven parameters. The description only restates the artifact type enum ('screenshot, analysis, report') without adding any new parameter-level meaning, which is the expected baseline when the schema already covers everything.

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 a specific verb and resource: 'Save an artifact (screenshot, analysis, report) to the company archive.' The artifact types add useful specificity, but it does not explicitly distinguish itself from similar siblings like save_knowledge, so it misses the top bar for explicit sibling differentiation.

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 gives clear usage context: 'Use after browse_url to persist visual evidence, or to save any agent-produced artifact for future reference.' It also explains the approval workflow and instructs not to re-ask in chat. It stops short of saying when not to use it or naming alternatives, so it earns a 4 rather than a 5.

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