forgepilot_create_artifact

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

With no annotations, the description carries the full burden, and it does disclose two real traits: the bundle is timestamped and read-only, and it includes a SHA-256 manifest. However, it does not state where the artifact is written, whether the call has side effects beyond producing the bundle, permission requirements, or whether it is idempotent.

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 the verb first and the resource's defining properties immediately after. Every clause adds information; nothing is wasted.

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 effectively outlines the produced artifact's composition, which partly substitutes for the absent output schema, but with no annotations and a fully undocumented required input parameter, an agent still lacks enough to invoke the tool confidently.

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?

There is a single required parameter ('request') with 0% schema description coverage, and the description says nothing about its expected format or content (e.g., JSON spec vs. natural-language instruction). The enumerated items (evidence, response, report, manifest) describe the output bundle, not the input, so the parameter remains opaque.

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 specific verb ('Create') and a well-defined resource (a timestamped, read-only integration run bundle), and enumerates the bundle's contents (evidence, response, report, SHA-256 manifest). It is clear what the tool produces, though it does not explicitly distinguish itself from close siblings like forgepilot_create_connector_artifact or forgepilot_create_shareable_pack.

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 statement of when to use this tool versus the other create_* siblings, no prerequisites, and no conditions or exclusions. The agent must infer usage entirely from the name and resource type.

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