Ghl Create Form

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

With no annotations, the description must carry the behavioral burden. It explicitly warns 'WRITES to the live account,' signaling mutation and real-world side effects, and states that the tool returns an id. It does not disclose auth requirements or idempotency, but the live-account warning is valuable transparency.

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 two short sentences with every phrase earning its place. The primary action and return value are front-loaded, followed by the critical side-effect warning. No filler or redundancy.

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 simple 2-parameter creation tool with an output schema, the description covers the core action, the return value, and the write side effect. However, it omits the meaning of 'location_id', any usage context, and any mention of permissions, leaving some practical gaps.

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 meaning for either parameter. 'name' may be inferred as the form's name, but 'location_id' remains completely unexplained, leaving an optional parameter without semantic context.

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 specific verb and resource: 'Create an empty form and return its id.' It clearly differentiates this creation tool from sibling list/read/update/delete tools, and 'empty form' adds precision about the operation's scope.

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 explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The intended use is only weakly implied by the name and 'Create an empty form.'

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