bridge_artifact_write

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

Annotations already provide idempotentHint=true and destructiveHint=false; the description adds non-obvious context by promising atomic persistence and scoping to an 'allowed bridge-owned data namespace'. No contradiction with annotations, but overwrite/conflict behavior is not detailed.

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?

A single, front-loaded sentence with no filler. The key guarantee ('Atomically') and the resource scope are presented first, and every phrase adds meaning.

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?

Despite concise atomic-write context and useful annotations, there is no output schema and no description of return values, path conventions, or error/overwrite behavior. For a required three-parameter write tool, an agent is left to infer too much.

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?

Input schema parameter descriptions are 0% covered, so the description must compensate. It tells the agent that content is text or structured and that the namespace is bridge-owned/allowed, but it says nothing about path semantics and gives only a vague type hint for content.

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 names a precise verb ('Atomically persist') and a specific resource ('text or structured reconstruction/source-registry artifact under an allowed bridge-owned data namespace'). It clearly separates this write tool from sibling read/search/review tools such as repo_read, repo_search, and rva_review_result.

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?

No guidance is given about when to prefer this tool over alternatives or when not to use it. It never references sibling tools or conditions such as 'use repo_read for reading' or 'use research_publish_knowledge for knowledge publication'.

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