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

The annotations indicate this is not read-only and not idempotent, but the description does not explain what posting an artifact does, whether artifacts are overwritten or versioned, who can see them, or what permissions are required. It also does not clarify that the get and list actions are read operations within a tool that also supports mutation.

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 wasted words, but the brevity comes at the cost of under-specification. It is concise without being sufficiently informative.

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?

For a tool with an action enum, a nested untyped params object, and no output schema, the description is far too thin. It does not explain the required params for each action or what the tool returns, leaving the agent unable to invoke it confidently beyond guessing.

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%, and the description provides no information about the params object, which is an untyped nested object. It loosely maps post/read/list to the action enum, but gives no details about what each action requires in params or how to format them.

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 three actions (post, read, list) and a resource category (contextual artifacts and deliverables), so the general purpose is inferable. However, "contextual artifacts" is vague and the description does not distinguish this tool from sibling tools such as handoff_task, handoff_work, or handoff_offer.

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?

There is no guidance on when to use this tool versus the many handoff_* siblings, nor when to choose post versus get versus list. The agent must infer all selection criteria from the tool name and schema.

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