gunkit_proxy

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing concrete: no side effects, no permission/auth requirements, no reversibility, no output or state impact. The metaphorical phrasing ('label every picture of it') actively obscures rather than informs.

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?

It is short, but the two sentences are jargon-dense and front-load an unclear metaphor rather than the operation. Size is not the problem; the content is opaque and non-actionable.

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?

With no annotations, no output schema, an undocumented required parameter, and a metaphorical description, an agent has essentially nothing needed to invoke this tool correctly. This is inadequate for even a single-parameter tool.

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 single required parameter 'action' has 0% schema description coverage, and the description never explains what 'action' means, its allowed values, or its format. The burden falls entirely on the description and it does not deliver.

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 gestures at creating a low-fidelity proxy/test model of a gun ('simple shapes with its real moving parts'), but the prose is metaphorical and never states a clean verb+resource. An agent cannot reliably tell what operation this performs versus siblings like gunkit_build, gunkit_rig, or gunkit_draft from this text alone.

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 when-to-use, when-not-to-use, or alternative guidance. The clause 'the whole chain runs on it before a real model exists' hints at a pipeline position but names no sibling and gives no selection criteria.

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