Export Terraform from an architecture

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

No annotations are provided, so the description must fully convey behavioral traits. However, it only states that the tool generates files and works offline. It omits critical details such as authentication requirements, whether existing files are overwritten, the output format, or any side effects. This leaves the agent with significant uncertainty about the tool's behavior.

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 concise (two short sentences), but it sacrifices completeness for brevity. It front-loads the core purpose but omits necessary details, making it insufficiently informative for a tool with a complex input schema.

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?

Given the complexity of the input schema (nested object with required fields) and the lack of an output schema, the description is incomplete. It fails to explain how to structure the architecture graph, what the output (Terraform files) entails, or any side effects. The agent cannot fully understand how to invoke the tool correctly without additional context.

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 description provides no explanation of the single parameter ('graph'), which has a complex nested schema. With 0% schema description coverage, the description should elaborate on how to structure the architecture graph, but it only vaguely references 'from an architecture graph' without any specifics about node/edge properties, required fields, or examples.

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 clearly states the tool's purpose: generating Terraform project files from an architecture graph. It uses specific verbs ('Generate') and resource ('Terraform project files'), and the offline note distinguishes it from tools that may require network access. This effectively separates it from sibling tools like pinpole_build_architecture or pinpole_simulate_cost.

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?

The description provides minimal usage guidance. It mentions 'Works offline' but does not specify when to use this tool versus alternatives, nor does it list prerequisites or exclusions. The agent is left to infer usage context from the tool name and siblings.

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