workflow_submit_artifact

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

No annotations are provided, so the description must carry the full behavioral burden. It implies a write/side-effecting operation but says nothing about idempotency, whether artifactId must be unique, what happens on conflicting contentHash, permissions required, or whether the artifact becomes visible to other tasks. The 0% schema coverage and lack of annotations leave significant behavioral gaps.

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 wasted words. It is appropriately sized, though the brevity contributes to the specifications gaps noted elsewhere.

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 5-parameter, 4-required mutation tool with no output schema and no annotations, the definition is incomplete. An agent cannot determine required permissions, idempotency behavior, how sections map to storage, or what a successful submission returns or enables. In a toolset of ~40 workflow siblings, this tool needs more context to be callable correctly.

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 adds no parameter detail. Required fields (taskId, artifactId, type, sections) are only inferable from the schema's structure; the enum's six report types and the semantics of contentHash are not explained. The description does not compensate for the complete lack of schema-level parameter documentation.

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 verb ('Persist') and a resource ('structured, human-readable workflow artifact produced by local Copilot'). It is somewhat clearer than the name alone, but 'Persist' is ambiguous here—unclear whether it means submit to a server, save to disk, or register with a workflow—and it does not distinguish this tool from siblings like workflow_sync_onboarding_artifact or workflow_get_related_artifacts.

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 related workflow tools (e.g., workflow_submit_decision, workflow_sync_onboarding_artifact, workflow_record_* variants). The phrase 'produced by local Copilot' hints at context but does not tell an agent when submission is required or how it relates to task or artifact retrieval.

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