forgepilot_create_connector_artifact

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

With no annotations, the description carries the full behavioral burden. It names the outputs but does not say whether files are written to disk, where they land, whether existing files are overwritten, or whether any permissions are needed for a tool with 'create' semantics — significant gaps for a mutating operation.

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 delivverable is stated immediately and every word earns its place.

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?

There is no output schema and no annotations, so the description should clarify the produced artifacts' form and destination. It names the artifacts but leaves the write-vs-return behavior unclear, making it only minimally adequate for an agent to invoke 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema. Baseline for a parameterless tool is 4; the description does confirm the implicit scope (current local checkout) that substitutes for input.

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 gives a specific verb (Generate) and concrete deliverables (Claude Code and Codex MCP configs plus bootstrap scripts), which clearly differentiates it from the vaguer generate_config sibling. It does not explicitly name which sibling it is not, but the artifact list makes the intent unambiguous.

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 states the artifact scope ('for the current local checkout') but offers no when-to-use guidance, no exclusions, and no routing away from close siblings like forgepilot_generate_config or forgepilot_create_artifact. An agent has to guess which of the generation tools to pick.

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